IBM Systems
IBM Systems Director Systems Management Guide
Version 6.1.1
GC30-4176-03



IBM Systems
IBM Systems Director Systems Management Guide
Version 6.1.1
GC30-4176-03
 Note
Before using this information and the product it supports, read the information in “Notices” on
page 723.

© Copyright International Business Machines Corporation 1999, 2009.

US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
About this publication . . . . . . . . ix
Conventions and terminology . . . . . . . . ix
Publications and related information . . . . . . ix
Web resources . . . . . . . . . . . . . xii
How to send your comments . . . . . . . . xiii
What’s new in version 6.1 . . . . . . xv
Documentation updates as of November 2008 . . xxii
Terminology changes . . . . . . . . . . xxxi
Chapter 1. Overview of IBM Systems
Director . . . . . . . . . . . . . . . 1
Accessibility . . . . . . . . . . . . . . 1
License information . . . . . . . . . . . . 1
IBM Systems Director technical overview . . . . . 2
IBM Systems Director components . . . . . . 3
Manageable resource types . . . . . . . . 7
Manageable systems . . . . . . . . . . . 7
User interfaces. . . . . . . . . . . . . 8
Base function and extensible plug-ins . . . . . 9
Upward integration. . . . . . . . . . . 15
I’m a 5.20 user. How do I use 6.1? . . . . . . . 16
Why am I starting at the Welcome page? . . . 16
What can I do with the rest of the interface? . . 30
How do I discover my systems? . . . . . . 32
How do I view my systems and groups? . . . 49
How do I view my inventory? . . . . . . . 67
Where are my tasks? . . . . . . . . . . 70
How do I start tasks? . . . . . . . . . . 71
How do I create a hardware event automation
plan? . . . . . . . . . . . . . . . 72
Chapter 2. Using the IBM Systems
Director Web interface . . . . . . . . 75
Logging into IBM Systems Director Server . . . . 75
Logging out of IBM Systems Director Server . . . 76
Navigating the Web interface . . . . . . . . 76
The Web interface . . . . . . . . . . . 76
Customizing the Web interface . . . . . . . 78
Managing and closing open pages in the Web
interface . . . . . . . . . . . . . . 79
Viewing help in the Web interface . . . . . . 80
Navigating IBM Systems Director by way of the
Welcome page . . . . . . . . . . . . . 80
IBM Systems Director Welcome page . . . . . 81
System severity states . . . . . . . . . . 88
Starting work in IBM Systems Director . . . . 89
Learning about the product . . . . . . . . 90
Checking IBM Systems Director readiness . . . 90
Viewing updates. . . . . . . . . . . . 91
Viewing tutorials . . . . . . . . . . . 92
Viewing the IBM Systems Director Server
summary . . . . . . . . . . . . . . 93
Finding and navigating resources . . . . . . . 95
© Copyright IBM Corp. 1999, 2009
Resource views . . . . . . . . . . . . 96
Finding systems and other resources . . . . 108
Viewing resources in the topology perspective 109
Working with tables . . . . . . . . . . 114
Working with topology maps . . . . . . . 127
Working with properties. . . . . . . . . 139
Setting navigation preferences . . . . . . . 142
Renaming a resource . . . . . . . . . . 144
Removing a resource . . . . . . . . . . 145
Managing groups . . . . . . . . . . . . 146
Groups . . . . . . . . . . . . . . 146
Creating a criteria-based dynamic group . . . 152
Creating a static group . . . . . . . . . 155
Editing a group . . . . . . . . . . . 156
Deleting a group . . . . . . . . . . . 157
Adding a resource to an existing group . . . 158
Exporting a group . . . . . . . . . . . 159
Importing a group. . . . . . . . . . . 160
Finding and starting tasks . . . . . . . . . 161
Launched tasks and the IBM Systems Director
Launched Tasks program . . . . . . . . 161
Finding a task . . . . . . . . . . . . 162
Starting tasks . . . . . . . . . . . . 163
Starting the IBM Systems Director Launched
Tasks program . . . . . . . . . . . . 164
Integrating external applications into IBM
Systems Director . . . . . . . . . . . 179
Scheduling tasks . . . . . . . . . . . . 199
Noninteractive tasks . . . . . . . . . . 199
Jobs and job instances . . . . . . . . . 200
Scheduling a task . . . . . . . . . . . 201
Scheduling a task from a selected system . . . 203
Viewing active and scheduled job information 205
Viewing information about scheduled jobs . . 207
Determining target systems that are affected by
a job . . . . . . . . . . . . . . . 208
Viewing job-instance records . . . . . . . 209
Viewing job-instance logs . . . . . . . . 210
Copying a scheduled job . . . . . . . . 212
Editing a scheduled job . . . . . . . . . 213
Running a scheduled job immediately . . . . 214
Suspending and resuming a scheduled job . . 215
Deleting a job . . . . . . . . . . . . 216
Managing auditing . . . . . . . . . . . 217
Audit records . . . . . . . . . . . . 217
Setting server-auditing preferences . . . . . 223
Viewing the audit log . . . . . . . . . 225
Deleting the audit log . . . . . . . . . 225
Encrypting interprocess communication . . . . 226
Encryption . . . . . . . . . . . . . 226
Enabling encryption . . . . . . . . . . 228
Disabling encryption . . . . . . . . . . 228
Changing the encryption algorithm . . . . . 229
Resending the encryption key to systems . . . 229
Creating a new encryption key . . . . . . 230
iii
Chapter 3. Discovering systems and Editing configuration plans. . . . . . . . 283
collecting inventory data . . . . . . 231 Exporting a configuration plan . . . . . . 283
Discovery . . . . . . . . . . . . . . 231 Importing a configuration plan . . . . . . 284
Discovery protocols . . . . . . . . . . . 232 Deleting configuration plans . . . . . . . 284
Viewing the discovery manager summary . . . . 233
Performing initial discovery . . . . . . . . 235 Chapter 5. Monitoring system status
Renaming discovered systems automatically . . . 236 and health. . . . . . . . . . . . . 285
Discovering systems with system discovery . . . 237 System status and health . . . . . . . . . 285
System discovery . . . . . . . . . . . 237 Viewing the status manager summary . . . . . 287
Performing a system discovery . . . . . . 237 Using the Health Summary task to view the status
Viewing system discovery results. . . . . . 239 of your environment . . . . . . . . . . . 288
Discovering systems with advanced system Scoreboard . . . . . . . . . . . . . 289
discovery . . . . . . . . . . . . . . . 239 Dashboard . . . . . . . . . . . . . 290
Discovery profiles . . . . . . . . . . . 239 Health summary . . . . . . . . . . . 290
Creating a discovery profile . . . . . . . 242 Using the scoreboard to identify issues . . . . 290
Managing discovery profiles . . . . . . . 256 Adding a graphical monitor to the dashboard 293
Performing an advanced system discovery . . 257 Removing a graphical monitor from the
Collecting and viewing inventory data . . . . . 259 dashboard . . . . . . . . . . . . . 293
Inventory data and collection profiles . . . . 259 Adding systems to the health summary . . . 294
Creating an inventory collection profile. . . . 261 Removing a group from the health summary 296
Managing inventory collection profiles . . . . 262 Using Navigate Resources to view the status of a
Collecting inventory . . . . . . . . . . 263 specific resource . . . . . . . . . . . . 296
Viewing inventory. . . . . . . . . . . 265 Managing monitors . . . . . . . . . . . 296
Resource-monitor attributes . . . . . . . 297
Chapter 4. Configuring systems . . . 267 Viewing a monitor . . . . . . . . . . 309
Configuration settings . . . . . . . . . . 267 Creating a monitor view. . . . . . . . . 310
Configuration templates . . . . . . . . . . 267 Editing a monitor view . . . . . . . . . 312
Configuration plans . . . . . . . . . . . 268 Deleting a monitor view. . . . . . . . . 313
The Automatically deploy feature . . . . . 269 Graphing a monitor . . . . . . . . . . 313
Predefined configuration plans . . . . . . 270 Creating a threshold . . . . . . . . . . 314
Configuration-setting license entitlement . . . . 270 Managing thresholds . . . . . . . . . . . 314
Monitoring the deployment of configuration plans Viewing a threshold . . . . . . . . . . 315
and configuration templates . . . . . . . . 270 Activating a threshold . . . . . . . . . 315
Managing system configuration . . . . . . . 272 Editing a threshold . . . . . . . . . . 315
Viewing configuration settings . . . . . . 272 Deactivating a threshold. . . . . . . . . 316
Editing configuration settings . . . . . . . 272 Deleting a threshold . . . . . . . . . . 316
Saving configuration settings as configuration Managing status set entries . . . . . . . . . 316
templates . . . . . . . . . . . . . . 273 Viewing a specific status set entry . . . . . 317
Saving configuration settings to a configuration Viewing status set entries for a specific resource 318
plan . . . . . . . . . . . . . . . 273 Viewing status set entries for a group of
Managing configuration templates . . . . . . 274 resources . . . . . . . . . . . . . . 318
Creating configuration templates . . . . . . 274 Activating a status set entry . . . . . . . 319
Creating a configuration template from an Deactivating a status set entry . . . . . . . 319
existing one . . . . . . . . . . . . . 275 Deleting a status set entry . . . . . . . . 320
Viewing configuration templates . . . . . . 276 Managing the event log . . . . . . . . . . 321
Editing configuration templates . . . . . . 276 Viewing events . . . . . . . . . . . . 321
Adding configuration templates to a Deleting an event . . . . . . . . . . . 322
configuration plan . . . . . . . . . . . 277 Changing event log preferences . . . . . . 322
Deploying configuration templates . . . . . 277 Managing SNMP devices . . . . . . . . . 323
Viewing deployed targets . . . . . . . . 278 Viewing SNMP device attributes . . . . . . 323
Exporting a configuration template . . . . . 278 Compiling a MIB file . . . . . . . . . . 324
Importing a configuration template . . . . . 279 Selecting MIB files to load into memory . . . 324
Deleting configuration templates . . . . . . 279 Managing process monitors . . . . . . . . 325
Managing configuration plans . . . . . . . . 279 Viewing process monitors . . . . . . . . 325
Creating configuration plans . . . . . . . 280 Creating a process monitor . . . . . . . . 325
Creating a configuration plan from an existing Applying a process monitor . . . . . . . 326
one . . . . . . . . . . . . . . . . 281 Removing all process monitors . . . . . . 327
Deploying configuration plans. . . . . . . 281 Monitoring system resources . . . . . . . . 327
Viewing configuration plans . . . . . . . 282 Recording resource-monitor statistics . . . . 327
Viewing deployment history . . . . . . . 282 Exporting resource-monitor statistics . . . . 328

iv IBMSystems Director Systems Management Guide

 Viewing a graph of a resource-monitor Update considerations for IBM System x and
recording . . . . . . . . . . . . . . 328 IBM BladeCenter . . . . . . . . . . . 411
Removing a resource-monitor record . . . . 329 Update considerations for Hardware
Running a command-line program on a managed Management Console (HMC) systems . . . . 414
system . . . . . . . . . . . . . . . 329 Update considerations for IBM i systems . . . 415
Creating a command definition . . . . . . 329 Update considerations for Linux systems . . . 415
Running a command definition . . . . . . 331 Update considerations for Power Systems
Restricting anonymous command execution . . 331 Firmware . . . . . . . . . . . . . . 416
Viewing the Update Manager Summary page . . 417
Chapter 6. Automating tasks . . . . . 333 Configuring update manager . . . . . . . . 417
Events, filters, and actions in event automation Getting started with updates . . . . . . . 417
plans . . . . . . . . . . . . . . . . 334 Changing update settings . . . . . . . . 418
Events. . . . . . . . . . . . . . . 334 Managing updates. . . . . . . . . . . . 421
Event filters . . . . . . . . . . . . . 335 Managing update groups . . . . . . . . 421
Event actions . . . . . . . . . . . . 340 Performing actions on updates . . . . . . 422
Monitoring operating-system specific events . . 361 Viewing information about updates . . . . . 431
Viewing the automation manager summary . . . 362 Keeping systems in compliance . . . . . . . 437
Managing event automation plans . . . . . . 363 Compliance policies . . . . . . . . . . 437
Viewing event automation plans associated with Modifying compliance policies . . . . . . 438
a resource . . . . . . . . . . . . . 363 Identifying systems that are out of compliance 439
Creating an event automation plan . . . . . 364 Resolving compliance issues . . . . . . . 440
Copying an event automation plan . . . . . 378 Showing installed updates . . . . . . . . 440
Editing an event automation plan . . . . . 379 Showing needed updates . . . . . . . . 441
Deactivating and activating an event automation Update types . . . . . . . . . . . . . 442
plan . . . . . . . . . . . . . . . 380 Update types for AIX. . . . . . . . . . 442
Viewing event automation plan properties. . . 381 Update types for System x and IBM
Deleting an event automation plan . . . . . 381 BladeCenter . . . . . . . . . . . . . 442
Managing event actions . . . . . . . . . . 382 Update types for HMC . . . . . . . . . 443
Creating an event action. . . . . . . . . 382 Update types for IBM Systems Director and
Editing an event action . . . . . . . . . 383 IBM Director . . . . . . . . . . . . 444
Copying an event action. . . . . . . . . 384 Update types for IBM i systems . . . . . . 444
Testing an event action . . . . . . . . . 385 Update types for Linux . . . . . . . . . 444
Deleting an event action . . . . . . . . . 386 Update types for Power Systems Firmware . . 445
Activating and deactivating an event-action
history . . . . . . . . . . . . . . 387 Chapter 8. Remotely accessing
Viewing an event-action history . . . . . . 388 systems and resources . . . . . . . 447
Refreshing an event-action-history log entries 390 Remote access facilities . . . . . . . . . . 447
Deleting event-action-history log entries . . . 390 Distributed Command . . . . . . . . . 447
Viewing event action properties . . . . . . 390 File transfer . . . . . . . . . . . . . 448
Event-data-substitution variables . . . . . . 391 Hardware command line . . . . . . . . 448
Managing event filters . . . . . . . . . . 394 Launch Web browser . . . . . . . . . . 449
Creating an event filter . . . . . . . . . 395 Remote command line . . . . . . . . . 449
Editing an event filter . . . . . . . . . 400 Remote control tasks . . . . . . . . . . 449
Copying an event filter . . . . . . . . . 401 Remote Xen Console . . . . . . . . . . 450
Viewing event filter properties . . . . . . 402 Serial Console . . . . . . . . . . . . 450
Viewing predefined filter criteria . . . . . . 402 Running remote access functions . . . . . . . 451
Deleting an event filter . . . . . . . . . 403 Using the Distributed Shell . . . . . . . . 451
Transferring files and directories . . . . . . 454
Chapter 7. Updating systems . . . . 405 Synchronizing files, directories, or drives . . . 455
Supported updates . . . . . . . . . . . 406 Changing the encoding for a file . . . . . . 455
| Supported System x and BladeCenter systems . . 407 Using the hardware command line . . . . . 455
Starting to monitor and update systems . . . . 407 Establishing a remote command-line session . . 456
Updates to IBM Systems Director and IBM Director 408 Launching a Web browser . . . . . . . . 456
Considerations for updating systems that have Configuring Microsoft Windows Remote
earlier versions of IBM Director . . . . . . 408 Desktop Connection . . . . . . . . . . 457
Updating IBM Systems Director . . . . . . 408 Establishing Remote Desktop Connection . . . 457
Update considerations for specific operating Establishing Virtual Network Computing
systems and platforms . . . . . . . . . . 409 communications . . . . . . . . . . . 457
Update considerations for AIX systems . . . . 409 Establishing IBM BladeCenter or RSA
communication . . . . . . . . . . . . 458
Establishing a remote Xen console session . . . 458

Contents v
 Using the serial console . . . . . . . . . 459 Power On/Off task support using out-of-band
communication . . . . . . . . . . . . 495
Chapter 9. Managing agents . . . . . 461 Power On/Off task support using Wake on
Common agent services . . . . . . . . . . 461 LAN technology on System x . . . . . . . 496
Installing agents using the Agent Installation Power On/Off task support by way of the
Wizard . . . . . . . . . . . . . . . 463 operating system on System x and blade servers 496
Importing agent packages . . . . . . . . . 466 Changing the power state on System x and IBM
Creating agent packages. . . . . . . . . . 467 BladeCenter hardware . . . . . . . . . 497
Setting the agent manager for IBM Systems Enabling collection of SNMP-based inventory by
Director Server . . . . . . . . . . . . . 469 way of management modules . . . . . . . . 498
Viewing the agent manager properties . . . . 469 Using hardware-log information from System x
Adding a new agent manager . . . . . . . 470 service processors and IBM BladeCenter products . 499
Setting the active agent manager . . . . . . 471 Hardware-log information using out-of-band
Deleting an agent manager . . . . . . . . 471 and in-band communication . . . . . . . 499
Using a remote agent manager with IBM Viewing hardware-log information . . . . . 500
Systems Director . . . . . . . . . . . 472 Refreshing hardware-log information . . . . 501
Managing the agent manager used by a Clearing the hardware-log information . . . . 501
Common Agent . . . . . . . . . . . 474 Providing hardware-log information. . . . . 502
Viewing the agent manager configuration . . . . 476 Using locator LED settings on IBM BladeCenter
Securing Common-Agent managed systems . . . 477 and System x servers . . . . . . . . . . . 503
Changing the agent registration password . . . 477 Locator LEDs and out-of-band and in-band
Migrating common agents to a different communication . . . . . . . . . . . . 503
management server . . . . . . . . . . . 480 Identifying hardware with the locator LED . . 504
Solving hardware problems using
light-path-diagnostic LEDs on IBM BladeCenter
Chapter 10. Managing IBM
and System x servers . . . . . . . . . . . 504
BladeCenter and System x systems. . 481 Light-path-diagnostic LED information . . . . 505
Supported IBM BladeCenter products . . . . . 481 Viewing light-path-diagnostics status . . . . 506
Service processor communication. . . . . . . 482 Viewing detailed light-path-diagnostics
In-band communication requirements . . . . 482 information . . . . . . . . . . . . . 507
Out-of-band communication requirements . . . 483 Changing the resource for viewing
Out-of-band communication and the standard light-path-diagnostics LED information . . . . 508
TCP Command Mode protocol . . . . . . 485 Configuring templates . . . . . . . . . . 508
Out-of-band communication and the secure TCP Password security levels for IBM BladeCenter
Command Mode protocol . . . . . . . . 486 management modules and System x service
Out-of-band alert-forwarding strategies. . . . 487 processors . . . . . . . . . . . . . 508
Service processors and resource types . . . . 487 Configuring the boot sequence for a blade
Viewing the IBM BladeCenter and System x server in an IBM BladeCenter chassis . . . . 510
management summary . . . . . . . . . . 488 Configuring an IBM BladeCenter management
Downloading and activating BladeCenter I/O module . . . . . . . . . . . . . . 511
module plug-ins . . . . . . . . . . . . 490 Configuring network resources for IBM
Configuring integrated management modules . . 491 BladeCenter blade servers . . . . . . . . 529
Integrated management module task support Configuring SNMP agent community
and features . . . . . . . . . . . . . 491 information . . . . . . . . . . . . . 531
Changing the integrated management module Configuring the IP address pool for IBM
IP address by way of the Server resource . . . 491 BladeCenter systems and System x servers . . 532
Changing the integrated management module Configuring System x service processors . . . 533
IP address by way of the System resource . . . 492 Configuring IBM BladeCenter switch module
Changing the network port on an integrated protocols . . . . . . . . . . . . . . 545
management module . . . . . . . . . . 492 Configuring the IBM BladeCenter switch
Configuring integrated management module module virtual LAN . . . . . . . . . . 548
security . . . . . . . . . . . . . . 493 Configuring users and passwords for an IBM
Configuring the Try DHCP setting for integrated BladeCenter chassis . . . . . . . . . . 550
management module . . . . . . . . . . 493 Managing network-configuration information 551
Enabling Secure Sockets Layer after discovery 493 Managing system-account information . . . . 553
Enabling Secure Sockets Layer before discovery 494 Setting asset information . . . . . . . . 556
Changing the password for the Remote Supervisor
Adapter or management module . . . . . . . 494
Chapter 11. Managing IBM Power
Managing power state settings on IBM BladeCenter
and System x servers . . . . . . . . . . . 495 Systems . . . . . . . . . . . . . 561
New terms for Power Systems users in IBM
Systems Director . . . . . . . . . . . . 561

vi IBMSystems Director Systems Management Guide

Managing Power Systems running AIX . . . . . 563
Managing Power Systems running IBM i . . . . 563
Managing systems controlled by HMC and IVM 564
Viewing the Power Systems Management summary 565
Monitoring for IBM i message queue events . . . 566
Managing power state settings on IBM Power
systems . . . . . . . . . . . . . . . 568
Power On/Off task support by way of the
operating system on IBM Power systems . . . 568
Changing the power state on IBM Power
systems . . . . . . . . . . . . . . 568
Chapter 12. Managing IBM System z
systems. . . . . . . . . . . . . . 571
System z virtualization . . . . . . . . . . 571
Basics about the z/VM operating system . . . . 571
z/VM manageability access point and agent . . . 574
Viewing the System z Management summary page 575
Discovering systems and collecting inventory data
for System z . . . . . . . . . . . . . . 576
Managing power state settings for Linux on
System z servers . . . . . . . . . . . . 577
Power On/Off task support by way of the
operating system on System z servers . . . . 577
Changing the power state on System z servers 577
Chapter 13. Managing and configuring
storage . . . . . . . . . . . . . . 579
Storage management in real time and using
configuration templates . . . . . . . . . . 579
Managing SMI-S providers . . . . . . . . . 579
SMI-S providers for IBM Systems Director. . . 579
Installing SMI-S Providers . . . . . . . . 582
Configuring SMI-S providers . . . . . . . 587
Discovering and collecting inventory for storage
devices . . . . . . . . . . . . . . . 590
Running Discovery and unlocking storage
devices using SMI-S providers. . . . . . . 590
Running Direct Connection discovery and
unlocking storage devices using SMI-S
providers . . . . . . . . . . . . . . 591
Running Advanced Discovery for multiple
SMI-S providers using multicast and broadcast . 593
Running Advanced Discovery for SMI-S
providers using a directory agent. . . . . . 594
Working with external storage applications . . . 595
Installing and configuring external storage
applications . . . . . . . . . . . . . 596
Launching an external storage management
application . . . . . . . . . . . . . 599
Viewing storage devices . . . . . . . . . . 601
Storage Management Summary . . . . . . 601
Viewing storage systems using storage groups 603
Displaying attached storage for a given system 603
Viewing storage volumes . . . . . . . . 604
Viewing the health and status of storage devices 604
Storage topology perspective . . . . . . . 605
Managing storage in real-time . . . . . . . . 606
Managing IBM BladeCenter and System x
storage devices . . . . . . . . . . . . 606
Adding IBM BladeCenter Integrated Storage
devices to a server. . . . . . . . . . . 609
Provisioning storage from an existing storage
subsystem . . . . . . . . . . . . . 610
Managing storage volumes in real time . . . . 611
Configuring iSCSI components in real time . . 614
Configuring IBM BladeCenter SAS zone
connectivity in real time . . . . . . . . . 619
Managing storage with configuration templates 621
Viewing storage configuration templates . . . 621
Changing storage configuration templates . . . 621
Creating a configuration template for a storage
volume . . . . . . . . . . . . . . 622
Managing IBM BladeCenter SAN configuration
mapping . . . . . . . . . . . . . . 622
Configuring iSCSI components using
configuration template . . . . . . . . . 626
Managing IBM BladeCenter SAS zone
configuration . . . . . . . . . . . . 630
Chapter 14. Managing virtual
environments . . . . . . . . . . . 635
Virtual systems . . . . . . . . . . . . . 635
Platform managers . . . . . . . . . . 635
Virtual farms . . . . . . . . . . . . 635
Hosts . . . . . . . . . . . . . . . 637
Virtual servers . . . . . . . . . . . . 638
Guest-operating-systems. . . . . . . . . 639
Virtualization groups . . . . . . . . . . . 639
Viewing the virtualization manager summary . . 640
Viewing resources in virtualization perspectives 641
In the Virtualization Basic perspective . . . . 641
In the Virtualization Common perspective . . . 641
In the Virtualization Detail perspective . . . . 641
Viewing resources in the Platform Managers and
Members view . . . . . . . . . . . . . 641
Viewing resources in the Virtual Servers and Hosts
view . . . . . . . . . . . . . . . . 642
Viewing virtualization properties . . . . . . . 642
Configuring virtual resources . . . . . . . . 643
Configuring Power Systems platform managers 643
Configuring storage resources . . . . . . . 648
Managing host systems . . . . . . . . . . 650
Entering maintenance mode . . . . . . . 650
Exiting from maintenance mode . . . . . . 650
Starting the virtualization service on a host . . 651
Stopping the virtualization service on a host . . 651
Managing virtual farms . . . . . . . . . . 651
Adding a host to a virtual farm . . . . . . 651
Creating a virtual farm . . . . . . . . . 652
Deleting a virtual farm from IBM Systems
Director and VMware VirtualCenter . . . . . 653
Removing a virtual farm from IBM Systems
Director . . . . . . . . . . . . . . 654
Editing a virtual farm . . . . . . . . . 654
Removing a host from a virtual farm . . . . 655
Starting the virtualization service on a farm . . 655
Stopping the virtualization service on a farm 655
Viewing virtual farms . . . . . . . . . 655
Managing virtual servers . . . . . . . . . 656
Connecting to a platform manager . . . . . 656
Contents vii
 Disconnecting from a platform manager . . . 657 Authorizing users to manage resources . . . . 699
Creating virtual servers . . . . . . . . . 657 Assigning a role to a user or user group . . . 700
Creating a virtual disk for Xen . . . . . . 671 Copying a role to another user . . . . . . 701
Deleting a virtual server permanently . . . . 672 Creating a role . . . . . . . . . . . . 701
Editing host resources . . . . . . . . . 672 Managing roles . . . . . . . . . . . . 702
Editing virtual servers . . . . . . . . . 673 Managing credentials in IBM Systems Director . . 704
Accessing the Xen remote console . . . . . 674 Credentials . . . . . . . . . . . . . 704
Managing power operations on virtual servers 675 Managing shared credentials . . . . . . . 705
Relocating virtual servers . . . . . . . . 677 Managing targeted credentials . . . . . . . 707
Launch VMware ESX Manager User Interface 685 Managing console access point credentials. . . 709
Launch VMware VirtualCenter Console . . . 685 Configuring the authentication registry . . . . 711
Launch VMware Infrastructure Client . . . . 686 Managing mappings . . . . . . . . . . 711
Launch Microsoft Virtual Server Console . . . 686 Managing access . . . . . . . . . . . . 713
Accessing a secured system with request access 714
Chapter 15. Security . . . . . . . . 687 Accessing a secured system with configure
Authenticating users to IBM Systems Director . . 688 access . . . . . . . . . . . . . . . 715
User authentication . . . . . . . . . . 688 Revoking access to a secured system . . . . 716
Users and user groups in IBM Systems Director 688 Encrypting passwords for database configuration 716
Authenticating IBM Systems Director users
stored in the local operating system . . . . . 690 Appendix. Accessibility features for
Authenticating IBM Systems Director users IBM Systems Director . . . . . . . . 719
stored in the domain server . . . . . . . 690
Authenticating IBM Systems Director users Notices . . . . . . . . . . . . . . 723
stored in LDAP. . . . . . . . . . . . 691
Trademarks . . . . . . . . . . . . . . 724
Editing user properties . . . . . . . . . 692
Authorizing users to IBM Systems Director . . . 693
User authorization. . . . . . . . . . . 693 Glossary . . . . . . . . . . . . . 727
Roles . . . . . . . . . . . . . . . 694
Permissions and roles required to run smcli
commands . . . . . . . . . . . . . 695

viii IBMSystems 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 www.adobe.com/products/
acrobat/readstep.html.

Information centers and topic collections

v IBM® Systems
publib.boulder.ibm.com/infocenter/systems/index.jsp
View the IBM® Systems information center which provides integrated
information for multiple IBM® Systems products, including operating systems,
hardware, storage, and software. This information center also contains scenarios
to help you use multiple IBM® Systems products in the same environment.
v IBM Systems Director
publib.boulder.ibm.com/infocenter/systems/topic/director_6.1/fqm0_main.html
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
publib.boulder.ibm.com/infocenter/systems/index.jsp

© Copyright IBM Corp. 1999, 2009 ix

 View the IBM® Systems information center for information about to install and
use plug-ins that extend the functionality of IBM Systems Director.
v IBM Systems Director Upward Integration Modules (UIMs)
publib.boulder.ibm.com/infocenter/systems/topic/uims/fqs0_main.html
Read the IBM Systems Director Upward Integration Modules (UIM) topic
collection to learn about how to install and use upward integration modules and
management packs that enable non-IBM® workgroup and enterprise-
management products to interpret and display data that is provided by
Common Agent and Platform Agent.
v IBM Systems Director Software Development Kit
publib.boulder.ibm.com/infocenter/dirinfo/toolkit/index.jsp
View the IBM Systems Director Software Development Kit (SDK) information
center to learn about the APIs and CLIs that you can use to extend the
capabilities of IBM Systems Director.

Publications
Release Notes® 6.1 and Release Notes 6.1.1
Provides information about hardware requirements for running IBM
Systems Director components, supported IBM Systems Director hardware,
operating systems, databases, and workgroup and enterprise
systems-management software.
Hardware and Software Support Guide
Provides information about hardware requirements for running IBM
Systems Director components, supported IBM Systems Director hardware,
operating systems, databases, and workgroup and enterprise
systems-management software.
Planning, Installation, and Configuration Guide for AIX®
Provides detailed instructions to install and configure each component of
IBM Systems Director on system running AIX using the standard
installation option.
Planning, Installation, and Configuration Guide for IBM i
Provides detailed instructions to install and configure each component of
IBM Systems Director on system running IBM i using the Standard
installation option.
Planning, Installation, and Configuration Guide for Linux® on Power Systems™
Provides detailed instructions to install and configure each component of
IBM Systems Director on system running Linux for Power Systems using
the Standard installation option.
Planning, Installation, and Configuration Guide for Linux on x86
Provides detailed instructions to install and configure each component of
IBM Systems Director on system running Linux for System x® using the
Standard installation option.
Planning, Installation, and Configuration Guide for Linux on System z®
Provides detailed instructions to install and configure each component of
IBM Systems Director on system running Linux for System z using the
Standard installation option.
Planning, Installation, and Configuration Guide for Windows®
Provides detailed instructions to install and configure each component of
IBM Systems Director on system running Windows using the Standard
installation option.

x IBMSystems Director Systems Management Guide

Systems Management Guide
Provides detailed instructions for using the Web interface and managing
systems and resources in your environment.
Troubleshooting Guide
Provides information about problems and how to solve them, and
strategies for troubleshooting common problems.
Events Reference
Provides information about IBM Systems Director events, including the
event type, description, severity, and extended attributes.
Commands Reference
Provides detailed information about the systems management
command-line interface (smcli) commands, and other commands that can
be run directly from the command line, including configuring the database,
and starting and stopping IBM Systems Director.
Hardware Command Line User’s Guide
Provides information about installing and using the Hardware Command
Line (formerly known as the IBM® Management Processor Command-Line
Interface). Command output in this release might vary from command
output in previous releases.

White papers and briefs

v IBM Systems Director
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 Managing IBM Power Servers with IBM Systems Director 6.1
www.ibm.com/common/ssi/fcgi-bin/ssialias?infotype=SA&subtype=WH
&appname=STGE_PO_PO_USEN&htmlfid=POW03011USEN
&attachment=POW03011USEN.PDF
Provides information about managing the virtualization and consolidation on
Power systems using IBM Systems Director.
v IBM Systems Director 6.1 Migration Tips
www.ibm.com/common/ssi/fcgi-bin/ssialias?infotype=SA&subtype=WH
&appname=STGE_XB_XB_USEN_&htmlfid=XBW03009USEN
&attachment=XBW03009USEN.PDF
Provides information about migrating data when upgrading your environment
from IBM Director V5.20 to IBM Systems Director V6.1.

IBM® Redbooks® publications

www.ibm.com/redbooks/

About this publication xi

 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.

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

Web sites
v IBM Systems Director
www.ibm.com/systems/management/director/
View the IBM Systems Director Web site on ibm.com® which provides links to
downloads and documentation for all currently supported versions of IBM
Systems Director.
v IBM Systems Director Downloads
www.ibm.com/systems/management/director/downloads/
View the IBM Systems Director Downloads Web site on ibm.com which provides
links to download code IBM Systems Director, IBM Systems Director plug-ins,
and IBM Systems Director upward integration modules.
v IBM Systems Director Documentation and Resources
www.ibm.com/systems/management/director/resources/
View the IBM Systems Director Documentation and Resources Web site on
ibm.com which provides links to product documentation, redbooks, redpapers,
white papers, and learning modules related to IBM Systems Director, IBM
Systems Director plug-ins, and IBM Systems Director upward integration
modules.
v IBM Systems Director Upward Integration
www.ibm.com/systems/management/director/upward/
View the IBM Systems Director Upward Integration Web site on ibm.com which
provides more information about IBM Systems Director upward integration
modules created by IBM® and other companies. IBM Systems Director UIMs
enable third-party workgroup and enterprise systems-management products to
interpret and display data that is provided by IBM Systems Director
Platform-Agent managed system.
v IBM® Servers
www.ibm.com/servers/
View the IBM® Servers Web site to learn about IBM® Systems server and storage
products.
v IBM® ServerProven®
www.ibm.com/servers/eserver/serverproven/compat/us/
View the IBM® ServerProven Web site to learn about hardware compatibility of
IBM® System x and BladeCenter® systems with IBM® applications and
middleware, including IBM Systems Director.

xii IBMSystems Director Systems Management Guide

 Forums
v IBM Systems Director
www.ibm.com/developerworks/forums/forum.jspa?forumID=759
View the IBM Systems Director forum Web site on ibm.com to discuss
product-related issues pertaining to IBM Systems Director, IBM Systems Director
UIMs, and IBM Systems Director extensions. This Web site includes a link for
obtaining the forum using a Rich Site Summary (RSS) feed.
v IBM Systems Director SDK
www.ibm.com/developerworks/forums/dw_esforums.jspa
View the IBM Systems Director SDK forum Web site to discuss issues pertaining
to the IBM Systems Director Software Development Kit (SDK). This Web site
includes a link for obtaining the forum using a Rich Site Summary (RSS) feed.
v IBM® Systems
www.ibm.com/developerworks/forums/dw_esforums.jsp
View the IBM® Systems forums Web site on ibm.com to learn about various
forums that are available to discuss technology-related and product-related
issues pertaining to IBM® Systems hardware and software products. This Web
site includes a link for obtaining the forum using a Rich Site Summary (RSS)
feed.

How to send your comments

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

If you have any comments about this book or any other IBM Systems Director
publication, go to the IBM Systems Director information center Web site at
publib.boulder.ibm.com/infocenter/systems/topic/director_6.1/fqm0_main.html.
There you will find the feedback page where you can enter and submit comments.

About this publication xiii

xiv IBMSystems Director Systems Management Guide
What’s new in version 6.1
IBM Systems Director Version 6.1 provides many new features and enhancements.
There are additional supported systems for installation and management. In
addition, some functions have changed in this version and some features have
been discontinued.

Hardware support

For information about hardware that is supported in this release, see the IBM
Systems Director Hardware and Software Support Guide.

Operating system support

IBM Systems Director 6.1 supports new operating systems and discontinues
support for some operating systems that are supported in Version 5.20. For
complete list of supported operating systems on each platform, see the IBM
Systems Director Hardware and Software Support Guide.

New operating system support

The following table lists operating systems that are supported by IBM Systems
Director 6.1 server and agents that were not supported in previous releases.
Table 1. New operating systems supported by IBM Systems Director 6.1
IBM
z/VM®
Manage-
IBM ability
Systems Access
Director Common Platform Point
Operating system Server Agent Agent Agent11
New operating systems supported on System x systems:
Windows Server 2008, Enterprise and Standard Editions (supports X
Service Pack 1)
Windows Server 2008, Enterprise and Standard x64 Editions X
(supports Service Pack 1)
Red Hat Enterprise Linux AS, ES, and WS, version 5.0, for AMD64 X
and EM64T, with Xen Kernel (Supports Updates 1 and 2)
SUSE Linux Enterprise Server 10, for AMD64 and EM64T, with X
Xen Kernel (supports Service Packs 1 and 2)
New operating systems supported on IBM Power systems:
Red Hat Enterprise Linux AS, version 4.7, on IBM Power systems X X X
Red Hat Enterprise Linux AS, version 5.2, on IBM Power systems X X X
SUSE Linux Enterprise Server 10 Service Pack 2 on IBM Power X X X
systems
New operating systems supported on System z systems:
Red Hat Enterprise Linux AS version 4.0 Updates 6 and 7 for X X X
System z systems

© Copyright IBM Corp. 1999, 2009 xv

Table 1. New operating systems supported by IBM Systems Director 6.1 (continued)
IBM
z/VM®
Manage-
IBM ability
Systems Access
Director Common Platform Point
Operating system Server Agent Agent Agent11
Red Hat Enterprise Linux AS version 5.0 Updates 2 and earlier for X X X
System z systems
SUSE Linux Enterprise Server 10 for IBM System z Service Pack 2 X X X X2
1
The IBM z/VM® Manageability Access Point Agent is used by IBM Systems Director 6.1.0 to monitor the
virtual machines and associated resources known as a z/VM system. The agent must be running in a virtual
machine within the IBM z/VM, version 5.4 system that is to be monitored.
2
IBM z/VM Manageability Access Point Agent requires SUSE Linux Enterprise Server 10 for IBM System z,
Service Pack 2.

Discontinued operating system support

The following table lists operating systems that are supported in Version 5.20 but
are not supported by IBM Systems Director Version 6.1 server and agents.
Table 2. Discontinued operating systems not supported by IBM Systems Director 6.1
IBM
Systems
Director Common Platform
Operating system Server Agent Agent
Discontinued operating systems on 32–bit System x systems and non-IBM® x86 system:
Windows 2000, Advanced Server and Server Editions (Service Pack 3 required; X X X
Service Pack 4 supported)
Windows 2000 Datacenter Edition X X
Windows 2000 Professional Edition (Service Pack 3 required; Service Pack 4 X X
supported)
Windows Small Business Server 2003, Windows Small Business Server 2003 R2 X X
Red Hat Enterprise Linux AS and ES, version 3.0 (supports Update 9 and earlier) X X X
Red Hat Enterprise Linux WS, version 3.0 (supports Update 9 and earlier) X X
VMware ESX Server (console), versions 2.5, 2.5.1, 2.5.2, 2.5.3, 2.5.4, 2.5.5, 3.0.2 X X
Update 1, and 3.0.3
VMware ESX Server (guest operating systems), versions 2.5, 2.5.1, 2.5.2, 2.5.3, X X X
2.5.4, 2.5.5, 3.0.2 Update 1, and 3.0.3
VMware GSX Server, versions 3.1 and 3.2, host operating systems X X
VMware GSX Server, versions 3.1 and 3.2, guest operating systems X X
®
Discontinued operating systems on 64–bit System x systems and non-IBM x86 system:
Windows Server 2003 Datacenter Edition for Itanium® systems X
Windows Server 2003 Enterprise Edition for Itanium systems X X
®
Red Hat Enterprise Linux AS, version 3.0, for Intel Itanium X X
Red Hat Enterprise Linux WS, version 3.0, for AMD64 and EM64T (supports X X
Update 9 and earlier)

xvi IBMSystems Director Systems Management Guide

Table 2. Discontinued operating systems not supported by IBM Systems Director 6.1 (continued)
IBM
Systems
Director Common Platform
Operating system Server Agent Agent
Red Hat Enterprise Linux AS, version 4.0, for Intel Itanium (supports Update 7 X
and earlier)
SUSE Linux Enterprise Server 9 for Itanium Processor Family X
®
Microsoft Virtual Server 2005 (Release 2 required; SP1 supported) X X X
Discontinued operating systems on IBM Power systems:
IBM AIX 5L™ Version 5.2 TL06 Service Pack 4 X
®
IBM i (formerly i5/OS ), Version 5 Release 3 X X
IBM i, Version 5 Release 4 X X
IBM i, Version 6 Release 1 X X
Red Hat Enterprise Linux AS, versions 4.3, 4.4, and 4.5 on IBM Power systems X X X
Red Hat Enterprise Linux AS, versions 5.0 on IBM Power systems X X X
Discontinued operating systems on System z systems:
Red Hat Enterprise Linux for Mainframe Computing (supports versions 5.1 and X X X
5.0)

Databases support
v IBM Systems Director Server V6.1 supports the following newer versions of
external databases:
– These databases are now supported:
- DB2/Express
– These databases are no longer supported:
- PostgreSQL
- Microsoft SQL Server 2000
- Microsoft Jet DB

For complete information about supported databases, see the IBM Systems Director
Hardware and Software Support Guide.

Functional enhancements
v Plug-in architecture: Function has been grouped in to components, called
plug-ins. These base plug-ins are provided with IBM Systems Director:
Discovery manager
Discovers both virtual and physical systems in your network, collects
inventory data about hardware and software, and visualizes
relationships to other systems in the network. This includes simple
unicast discovery and more advanced discovery workflows to discover,
authenticate and inventory one or more specific systems in the network.
Status manager
Monitors hardware status, power status, and update compliance status
on discovered systems. Using status manager, you can create, view, and
customize the resources and processes to monitor and generate
notifications when a custom threshold is reached.
Update manager
Acquires, distributes and installs required firmware, device drivers and
What’s new in version 6.1 xvii
 operating system updates using predefined policies and workflows.
Using update manager, you can also update IBM Systems Director
Server and agents and get updates to support hardware changes without
an upgrade or migration of the installed product.
Automation manager
Automatically performs predefined actions in response to events that
occur in your environment using event automation plans. Actions can
include sending an email, running a task on the management server, or
running a task on the system where the event was generated.
Configuration manager
Configures system parameters and hardware settings on systems,
including BladeCenter chassis and its installed components, in your
network. You can also set up configuration manager to automatically
configure newly discovered systems.
Remote access manager
Provides a set of integrated tools that support remote access, including
remote control tools (such as Virtual Network Computing (VNC),
Remote Desktop (RDP), and web-based remote control for IBM
BladeCenter and RSA), hardware command line, remote command line,
and file transfer tools.
Virtualization manager
Manages the lifecycle of your virtual resources (such as virtual servers
and virtual farms) from a single interface for many of the different
virtualization technologies. The virtualization tasks can be included in
event automation plans.
IBM System Storage™ management
Provides full lifecycle management of your storage resources including
discovery, status, configuration and updates.
IBM BladeCenter and System x management
Provides full lifecycle management of your modular System x, IBM
BladeCenter Chassis, and related resources including discovery, status,
configuration, updates, and virtualization.
IBM Power Systems management
Provides full lifecycle management of your IBM Power systems and
related resources including discovery, status, configuration, updates, and
virtualization.
IBM System z management
Provides the capability to discover System z systems and their associated
virtual servers, and to access status information about them.
v Simplified installation and deployment:
– Standard and custom installation options and enhanced unattended
installation streamlines the base installation of IBM Systems Director Server
– Automatic start of IBM Systems Director Server after successful installation
(Windows only)
– Migration tool that imports custom data from a previous release.
v Web-based user interface: A new flexible, intuitive user interface is integrated
with the IBM Systems Director Server and is accessible through any supported
Web browser that is connected to the management server. You no longer need to
install a console. Improvements include:

xviii IBMSystems Director Systems Management Guide

 – Welcome pages to assist you with setting up IBM Systems Director Server and
to determine whether actions are needed after IBM Systems Director Server is
up and running
– Resource views that list your systems and groups, show relationships
between resources, and list resource properties
– Navigation links to help you quickly find and perform tasks
– New wizards to walk you through certain tasks, such as creating groups
– Create and manage resource groups
– Tutorials to help you learn how to use features and functions available with
IBM Systems Director
Some tasks have not been ported to the new Web interface but can be launched
from the Web interface. These launched tasks are dynamically uploaded to the
system on which the browser is running to seamlessly perform the
launch-in-context of the task.
v Online help system enhancements: A new help system is available with
advanced search capabilities and an integrated table of contents. Organization
and related links have also been improved. Links from the Web interface display
context-sensitive help for the panel that you are currently viewing and also the
full help system.
v Discovery and inventory data collection enhancements:
– Basic discovery to find systems with a specific network address or range of
addresses
– Advanced discovery to find systems using a discovery profile, which
identifies the type of resources to discover and the discovery protocols to use,
automatically authenticates discovered systems, and collects inventory data
– Improved support for IBM Power, System z, and IBM System Storage systems
v System status and health enhancements:
– Scoreboard to easily monitor the health of your systems, including hardware,
thresholds and compliance status
– Dashboard to view graphical representations of live-data monitors for critical
resources
– Health summary to monitor the resources you care about most
– LED status of System x and blade servers
– Drill down to the root cause or problems
v Agent management enhancements: New tasks are available to deploy, install
and configure Common Agent and manage common agent services.
v Update management enhancements:
– Compliance policies to verify the currency of updates on systems.
– Search capabilities for update documentation files
v Event automation plans enhancements:
– Simplified interface for managing event automation plans, including new
wizards to easily set up email notifications or run a task
– Common event schema for heterogeneous systems
– New commands for managing event automation plans, event actions, event
filters, and event logs

Tip: Event automation plans were known as event action plans in the previous
release.
v Security enhancements:

What’s new in version 6.1 xix

 – Role-based authorization allows users to perform specific GUI and CLI tasks
and access specific resources
– Authorization through LDAP groups
– New set of default user roles
– Single sign-on (SSO) authentication using credentials for local and target
systems.
– Ability to specify credentials for a specific protocol or system, and to view
and edit credentials on specific systems
– New command line support for user groups, roles, and permissions
v System configuration enhancements:
– Integrated operating-system configurations settings for network, user
administration, SNMP agent settings, and inventory data
– Ability to create, view and edit template settings per system and integrate
into a configuration plans
– Improved support for IBM BladeCenter and IBM System Storage systems
v Remote management enhancements: Several new tools are available for
performing remote tasks, including launching Virtual Network Computing
(VNC) and Remote Desktop (RDP), from the Web interface
v Virtualization enhancements: IBM Virtualization Manager has been integrated
into IBM Systems Director base suite of tools to support the discovery, health,
and lifecycle tasks.
v Platform management enhancements:
– Support has been improved for managing your storage products, including
the seamless integration of Storage Configuration Manager and the ability to
launch external applications from the Web interface.
– Ability to launch IBM Systems Director Console for AIX from the IBM
Systems Director Web interface.
– Integration of IBM Systems Director Navigator for i5/OS into IBM Systems
Director Web interface.
v Storage management enhancements:
– Seamless integration of Storage Configuration Manager (SCM) function
– Ability to launch storage management application, such as TotalStorage®
Productivity Center (TPC)), from the Web interface
– Support for additional storage systems
v Command-line interface enhancements:
– Systems management command-line interface (smcli): The name of the
command-line interface has changed to smcli. The dircli command-line
interface is supported in this release for backward compatibility. All smcli
commands will run using either smcli or dircli. However, to use the
command syntax supported in IBM Director version 5.20 and earlier, you
must set the CLILEGACY environment variable. For more information, see
IBM Systems Director Commands Reference.
– New commands for systems, inventory, status, scheduler, user
administration, automation, process management and resource monitoring
commands: The command-line interface has been enhanced with new
commands to support systems, inventory, status, scheduler, user
administration, automation, process management and resource monitoring.
For a complete list of commands, see IBM Systems Director Commands
Reference.

xx IBMSystems Director Systems Management Guide

Discontinued function
v IBM Director base function: The following base function that was available in
IBM Director V5.20 is not supported in this release:
– License administration is not supported: License Administrator is no longer
supported in IBM Systems Director. In the previous release, you used License
Administration to view the total number of product licenses, the number of
used licenses, and the number of available licenses.
– Rack management is not supported: Rack Manager is no longer supported in
IBM Systems Director. In the previous release, you used Rack Manager to
group your systems in visual representations of rack suites.
– Remote Control tool has been replaced: Remote Control function has been
replaced with third-party tools, including Virtual Network Computing (VNC)
and Remote Desktop (RDP).
– Associations are no supported: Associations changed the organization of a
group of managed objects. This is not longer supported.
– High availability is not supported: High availability configurations are not
currently supported by IBM Systems Director.
– Microsoft Cluster Management is not supported: You can no longer monitor
the status of clusters in your network using the Microsoft Cluster Browser.
– Discontinued event actions: These event actions have been discontinued:
- Add a Message to the Console Ticker Tape
- Send an Event Message to a Console User
- Update the Status of the “event” System
v IBM Director V5.20 extensions The following extensions that were available in
IBM Director V5.20 are not supported in this release:
– Capacity Manager extension is not supported: Capacity Manager is no
longer a supported extension of IBM Systems Director. Capacity Manager was
a resource-management planning tool that you can use to monitor critical
resources (for example processor usage, hard disk capacity, memory usage,
and network traffic), identify current or potential bottlenecks, generate
performance-analysis reports, recommend ways to improve performance and
prevent diminished performance or downtime, and forecast performance
trends.
– Server Storage Provisioning Tool has been integrated into IBM Systems
Director: Server Storage Provisioning Tool function and commands have been
integrated into IBM Systems Director in the storage manager plugin. The
commands are now called storage commands.
– ServeRAID™ Manager extension is not supported: ServeRAID Manager is no
longer a supported extension of IBM Systems Director. IBM Systems Director
does perform inventory collection, monitor status, and raise events for RAID
controllers.

Tip: You can launch the ServeRAID Manager as an external application from
the IBM Systems Director Web interface; however, the application does not
recognize IBM Systems Director systems, groups, or clusters.
– Software Distribution Premium Edition extension is not supported:
Software Distribution Premium Edition is no longer a supported extension of
IBM Systems Director. Software Distribution Premium Edition was used to
import applications and data, build a software package, and distribute the
package to managed systems.
– System Availability is not supported: System Availability is no longer a
supported extension of IBM Systems Director. System Availability was an

What’s new in version 6.1 xxi

 analysis tool that you used to view statistics about system uptime and
downtime, identify problematic systems that have had too many unplanned
outages over a specified period of time, identify system that have old
availability data, and identify system that fail to report data.
– z/vm Center extension is not supported: z/vm Center is no longer a
supported extension of IBM Systems Director. z/VM Center used the z/VM
hypervisor to provision System z resources in form of z/VM virtual servers.
v The dircmd command-line interface and some dircli commands are
discontinued: All dircmd commands and several dircli commands that were
supported in IBM Director version 5.20 and earlier are no longer supported. In
most cases, equivalent functionality is implemented through commands in the
smcli command-line interface. For a complete list of supported commands, see
IBM Systems Director Commands Reference.

Documentation updates as of November 2008

Corrections to the documentation since the product was made available have been
provided in the IBM Systems Director information center in English. The IBM
Systems Director information center includes updates to both the printed and
online documentation. These corrections are not available in the online helps that
are viewable from the IBM Systems Director Web interface.

Users of translated information should consider these facts:

v Documentation corrections in the IBM Systems Director information center are
only in English and have not been translated into other languages.
v The English documentation is updated more frequently than the translated
documentation; when discrepancies occur between translated documentation
and the English documentation, rely on the English documentation.

The following sections identify the corrections that have been made to specific
topics in the IBM Systems Director documentation. The bold text is the title of the
topics that have changed.

Overview
v “IBM Systems Director technical overview” on page 2: Linux on System z
running on a partition without z/VM was added to the list of supported
systems for IBM System z management.
v “Platform Agent” on page 6: This topic changed to indicate that Platform Agent
is equivalent to IBM Director Core Services 5.20.3, not 5.20.
v “Additional IBM Systems Director plug-ins” on page 14:
– The Web page that is referenced for a complete list of available plug-ins and
for downloading plug-ins has changed to the following Web page:
www.ibm.com/systems/management/director/plugins/
– BladeCenter Open Fabric Manager plug-in is a for-fee plug-in that supports all
platforms that IBM Systems Director supports. The helps incorrectly state that
it is a free plug-in.
– The name of the Service and Support Manager plug-in is incorrectly called
Electronic Service Agent™ in the online help. 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.
v “Web resources” on page xii: Information and a URL for the IBM Systems
Director Best Practices wiki has been removed. This wiki does not exist.

xxii IBMSystems Director Systems Management Guide

v “Publications and related information” on page ix: Links to PDFs, white
papers, and redbooks have been added to the information center. These links are
not in the online help.

Planning
v “Virtualization software supported by IBM Systems Director”
(publib.boulder.ibm.com/infocenter/systems/topic/director.plan_6.1/
fqm0_r_supported_virt_software_versions.html): This topic has been updated to
indicate that PTF MH01146 is required for Hardware Management Console
Version 7.3.3 SP2.

Installing
v Extensive changes have been made to most of the installing topics.

Upgrading and migrating IBM Systems Director

v The upgrading and migrating topics have been updated to include information
about the IBM Systems Director Migration Tool, a new command-line utility that
is available for migrating data from IBM Director 5.20 to a new installation of
IBM Systems Director 6.1.

Configuring after installation

v “Configuring the command line interface”
(publib.boulder.ibm.com/infocenter/systems/topic/director.configdir_6.1/
fqm0_t_cm_configuring_cli.html): This topic has been added to provide steps
need to ensure that required software is installed and the locale is correctly
installed and configured on the system

Using the Web interface

v “Importing a group” on page 160: This topic has changed to also include static
groups. Both static and dynamic groups can be imported.
v “Exporting a group” on page 159: This topic has changed to also include static
groups. Both static and dynamic groups can be exported.
v “Default or predefined groups” on page 147: The following notes have been
added to the Group by System Type section:
For the Power Systems Blade Servers group

Note: The JS21 and JS22 blade servers are not displayed in this group.
They are displayed in the Power Server group that is contained in the
IBM Power Systems group.
For the Power Servers group

Note: The JS21 and JS22 blade servers are displayed in this group also.
v “Logging into IBM Systems Director Server” on page 75: A recommendation
that no more than 50 users log into IBM Systems Director Server at one time has
been changed to 30 users.

Discovering and inventorying systems

v “Discovery profiles” on page 239: This topic has been updated with a
description of the default advanced discovery profiles.

What’s new in version 6.1 xxiii

 Monitoring system status and health
v “Running a command definition” on page 331: A note was added to this topic
stating that using the command automation task to launch interactive programs,
for example notepad.exe, is not supported.
v “Viewing SNMP device attributes” on page 323: Several references to
configuring SNMP devices (including in the topic title) have been removed and
the following note has been added to this topic:

Note: To configure your SNMP devices, see ″Accessing a secured system with
configure access.″

Remotely accessing systems

v “Remote access facilities” on page 447: Two tools have been added to this page:
Launch Web Browser - Opens a browser window for the selected system
Remote Xen Console - Establishes command-line access to a remote Xen
server
v “Launch Web browser” on page 449: This is a new topic that describes the
Launch Web Browser tool, which you can use 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.
v “Remote Xen Console” on page 450: This is a new topic that describes the
Remote Xen Console tool, which is 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.
v “Launching a Web browser” on page 456: This is a new topic that describes
how to use the Launch Web browser task to access the default Web page for a
system that hosts a Web server.
v “Establishing a remote Xen console session” on page 458: This is a new topic
that describes how to establish a remote Xen console session.

Managing Power systems

v “Managing Power Systems running AIX” on page 563: This topic has changed
to indicate that you must have SMAdministrator authority for IBM Systems
Director to access the AIX management tasks.
v “Managing systems controlled by HMC and IVM” on page 564: The steps for
accessing HMC and IVM management tasks have been corrected.

Managing and configuring storage

v “Storage Management Summary” on page 601: This sentences has been added
to the description of the Capacity Summary section.
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 usable capacity and Total available capacity is not
included in the Capacity Summary for these storage devices.
v “Creating a storage volume from scratch” on page 612: Step 2 has been
changed to the following text:
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

xxiv IBMSystems Director Systems Management Guide

 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.
v “Creating a storage volume from a configuration template” on page 613: Step 7
has been changed to the following text:
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.
v “Installing the LSI ESG SMI-S provider on AIX and Linux systems” on page
584: This is a new topic that has been added to provide installation instructions
for the LSI ESG SMI-S provider, used for IBM TotalStorage DS4000® storage
systems, on Linux and AIX systems. Instructions for installation on Windows
systems already existed.
v “Provisioning storage from an existing storage subsystem” on page 610: Step 6
has been changed to the following text:
– Click Actions → System Configuration → Storage Resources
v “Verifying the LSI ESG SMI-S provider” on page 589: Step 6 has been changed
to the following text:
Right click on the entry LSISSI_StorageManagementSystem.
v “Installing the LSI ESG SMI-S provider on Windows systems” on page 584:
Step 1 has been changed to the following text:
Run the installation exec, such as Windows_Installer-WS32-10.35.30.00.exe.
The InstallAnywhere welcome page is displayed.
v “Managing IBM BladeCenter Integrated RAID Controllers and their attached
storage devices” on page 607: Steps 4 and 7 have been deleted.
v “Managing IBM BladeCenter SAS Connectivity Modules and their attached
storage devices” on page 608: Steps 2, 3, 4, 7, 10, and 13 have been deleted.
v “Managing IBM BladeCenter S SAS RAID Controller Modules and their
attached storage devices” on page 608: Extensive changes have been made to
this task.
v “Installing the SMI-S provider for the IBM BladeCenter S SAS RAID
Controller Module on additional systems” on page 583: The following
information has been added to this task:
There is a limitation that this SMI-S provider on any one system can manage
only four IBM BladeCenter chassis.
The SMI-S provider for the IBM BladeCenter S SAS RAID Controller Module
has one of these operating-system dependent names: v
PlatformAgentSubagent IBM BladeCenter SAS RAID Controller Module 6.1.0
Linux or PlatformAgentSubagent IBM BladeCenter SAS RAID Controller
Module 6.1.0 Windows
Before installing the PlatformAgentSubagent IBM BladeCenter SAS RAID
Controller Module 6.1.0 Linux or PlatformAgentSubagent IBM BladeCenter
SAS RAID Controller Module 6.1.0 Windows, ensure that you have already
installed Platform Agent on the managed system. It is possible to install the
subagent without this prerequisite, but the installation will complete with
errors and you will not be able to use the subagent.
v “Configuring the SMI-S provider for the IBM BladeCenter S SAS RAID
Controller Module” on page 587: Step 1 has been changed to the following text:
Type the User ID and Password for the management port. The default User
ID and Password are USERID1 and PASSW0RD (with a zero). These should
be used unless they have been changed.

What’s new in version 6.1 xxv

 v “Storage devices that require an SMI-S provider” on page 581: The following
information has been added to this concept:
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:
PlatformAgentSubagent IBM BladeCenter SAS RAID Controller Module 6.1.0
Linux or PlatformAgentSubagent IBM BladeCenter SAS RAID Controller
Module 6.1.0 Windows
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.
v “SMI-S providers for IBM Systems Director” on page 579: The following
information has been added to this concept:
The default port number for the SMI-S provider for the IBM BladeCenter® S
SAS RAID Controller Module will be 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 in order to use the default port on
Linux.
v “Running Direct Connection discovery and unlocking storage devices using
SMI-S providers” on page 591:
– The following text has been added to Step 12:
If you selected a Hardware type of IBM BladeCenter S SAS RAID
Controller Module, you cannot select a protocol. http protocol will always
be used.
– Two new steps were added between Step 14 and Step 15:
- If you selected a Hardware type of IBM system storage DS3000/DS4000,
the default port number is 5988.
- If you selected a Hardware type of IBM BladeCenter S SAS RAID
Controller Module, the default port number displayed will be 5988. This
might not be correct, depending on the operating system that hosts this
SMI-S provider. Review these choices and correct the port number if
necessary.
v 5988 is the default port number for the SMI-S provider of the IBM
BladeCenter S SAS RAID Controller Module when running on Microsoft
Windows 2003.
v 15988 is the default port number for the SMI-S provider of the IBM
BladeCenter S SAS RAID Controller Module when running on Linux.
v “Installing and configuring ServeRAID Manager” on page 598: Extensive
changes have been made to this task.
v “Requirements for ServeRAID Manager” on page 601: Extensive changes have
been made to this task.

xxvi IBMSystems Director Systems Management Guide

Managing virtual environments
v “Configuring credentials for the FSP CIM Proxy” on page 647: This topic has
been added to enable power on and power off functionality for IVM-managed
Power System servers or standalone Power System servers.
v “Removing a virtual farm from IBM Systems Director” on page 654: This topic
has changed to reflect that Xen no longer requires the virtualization manager
subagent.
v “Managing power operations on virtual servers” on page 675: Topics in this
section have changed to indicate that you must select the ″Power On/Off″ task
category from the Actions menu for managing power operations on virtual
servers.
v “Virtual server relocation” on page 677: This topic has changed to reflect that
Xen no longer requires the virtualization manager subagent.
v “Live relocation” on page 679: This topic has changed to reflect that Xen no
longer requires the virtualization manager subagent.

Security
v “Configuring the authentication registry” on page 711: This topic has been
added.
v “Encrypting passwords for database configuration” on page 716: This topic has
changed to indicate that when you must provide the information requested by
the script and then press Enter after every answer.
v “Authenticating IBM Systems Director users stored in LDAP” on page 691:
The steps in this topic have changed significantly.

Troubleshooting
v Changes have been made to several topics and many topics have been added to
this section.

Commands reference
v --help option: The following tip has been added to --help option that appears in
every command description for displaying man pages. This note is not in the
man pages or command line help.

Tip: (AIX and Linux only) You can also display detailed help in the form of
man pages using the man -t command_name command.
v “chfarm command”
(publib.boulder.ibm.com/infocenter/systems/topic/director.cli_6.1/
fqm0_r_cli_chfarm.html): The URL for the IBM® Virtualization Manager v1.2
information center was incorrect. The correct URL is: publib.boulder.ibm.com/
infocenter/eserver/v1r2/topic/eica7/
eica7_reference_command_info_commands.htm
v “mkfarm command”
(publib.boulder.ibm.com/infocenter/systems/topic/director.cli_6.1/
fqm0_r_cli_mkfarm.html): The URL for the IBM® Virtualization Manager v1.2
information center was incorrect. The correct URL is: publib.boulder.ibm.com/
infocenter/eserver/v1r2/topic/eica7/
eica7_reference_command_info_commands.htm
v “mkrelocatetask command”
(publib.boulder.ibm.com/infocenter/systems/topic/director.cli_6.1/
fqm0_r_cli_mkrelocatetask.html): The URL for the IBM® Virtualization Manager
v1.2 information center was incorrect. The correct URL is:

What’s new in version 6.1 xxvii

 publib.boulder.ibm.com/infocenter/eserver/v1r2/topic/eica7/
eica7_reference_command_info_commands.htm
v “Virtualization commands”
(publib.boulder.ibm.com/infocenter/systems/topic/director.cli_6.1/
fqm0_r_cli_virtualization_cmds.html): The URL for the IBM® Virtualization
Manager v1.2 information center was incorrect. The correct URL is:
publib.boulder.ibm.com/infocenter/eserver/v1r2/topic/eica7/
eica7_reference_command_info_commands.htm
v “chusregp command”
(publib.boulder.ibm.com/infocenter/systems/topic/director.cli_6.1/
fqm0_r_cli_chusergp.html): The syntax in the second example has been
corrected. The delimiter between the group names should be a semicolon (;), not
a comma.
smclichusergp -e role2:group1;group2 mygroup
v “dirinstall.server command”
(publib.boulder.ibm.com/infocenter/systems/topic/director.cli_6.1/
fqm0_r_cli_dirinstall_server.html): This is a new topic that describes the
dirinstall.server command. This command is used to install IBM Systems
Director on a management server running AIX or Linux.
v “discover command”
(publib.boulder.ibm.com/infocenter/systems/topic/director.cli_6.1/
fqm0_r_cli_discover.html): The syntax for the discover command incorrectly
placed the [-t system_type] option before the [-i ip_address_list] option.
Use the following corrected syntax:
smcli discover [-L language] [-v] [-W seconds] [{[-i] ip_address_list
[-t system_type]} | -p {all | profile_list}]
v “lsjobhistory command”
(publib.boulder.ibm.com/infocenter/systems/topic/director.cli_6.1/
fqm0_r_cli_lsjobhistory.html): The follow description has been removed:
If you do not specify any listing options, this command lists job names and
the job-instance IDs for those jobs.
v “lstask command”
(publib.boulder.ibm.com/infocenter/systems/topic/director.cli_6.1/
fqm0_r_cli_lstask.html): The registered trademark symbols has been removed
from the BladeCenter terms in the second example:
smcli lstask -oT "BladeCenter Assistant/BladeCenter Configuration"

BladeCenter Assistant/BladeCenter Configuration, 0x3D

v “mkcfgtmpl command”
(publib.boulder.ibm.com/infocenter/systems/topic/director.cli_6.1/
fqm0_r_cli_mkcfgtmpl.html):
– The following return codes have been added:
- 58: A template with the specified name and subtype already exists.
- 61: The input XML is not valid.
- 125:An internal error occurred.
v “mknspath command”
(publib.boulder.ibm.com/infocenter/systems/topic/director.cli_6.1/
fqm0_r_cli_mknspath.html): In the syntax, -wip_address_list has been changed
to -i ip_address_list. The complete syntax is:
smcli mknspath [-L language] [-v] [-A attribute_list] [-f file_name | -w
query | -i ip_address_list | -N group_list | [-n] system_list]
v “smreset command”
(publib.boulder.ibm.com/infocenter/systems/topic/director.cli_6.1/

xxviii IBMSystems Director Systems Management Guide

 fqm0_r_cli_smreset.html): The -l option has been added to the syntax and
option description. The -l option displays verbose messages and a non-zero exit
status to standard output.
v The following commands have been added as part of the IBM Systems Director
Migration Tool command-line utility:
– “smexport command”
(publib.boulder.ibm.com/infocenter/systems/topic/director.cli_6.1/
fqm0_r_cli_smexport.html)
– “smimport command”
(publib.boulder.ibm.com/infocenter/systems/topic/director.cli_6.1/
fqm0_r_cli_smimport.html)

User interface reference

v “Import Groups window”
(publib.boulder.ibm.com/infocenter/systems/topic/director.console_6.1/
fqm0_r_panel_import_groups.html): This topic has changed to also include
static groups. Both static and dynamic groups can be imported.
v “Location window”
(publib.boulder.ibm.com/infocenter/systems/topic/director.console_6.1/
fqm0_r_panel_rn_location_properties.html): A help topic has been added
describing the Location window provided by the Service and Support Manager
plug-in or the Active Energy Manager plug-in.
v Management Module Ports Configuration page: Remote presence port
information has been added. This is the default port number for remote
presence. The default value is 3900.
v “Remote Access Summary page”
(publib.boulder.ibm.com/infocenter/systems/topic/director.remote_6.1/
fqm0_r_panel_remote_access_summary_page.html): Two new options have been
added to this page:
Launch Web browser - Launches a Web browser for a system that hosts a
Web server
Remote Xen console - Communicates with a remote Xen server or host
v “Storage Management Summary page”
(publib.boulder.ibm.com/infocenter/systems/topic/director.storage_6.1/
fqm0_r_panel_storage_management.html): In the Capacity Summary section,
the following limitation has been added to the Local storage row for the Total
usable capacity and Total available capacity columns.
Capacity information collected for local storage devices attached to systems
that are running IBM Director 5.20 is limited to the Total raw capacity
column. The Total usable capacity and Total available capacity columns are
zero.
v “Storage Volumes page”
(publib.boulder.ibm.com/infocenter/systems/topic/director.storage_6.1/
fqm0_r_panel_storage_boot_bundle.html): The description of the Volume prefix
field in the Fields section has changed. 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.
v “Create Volume page”
(publib.boulder.ibm.com/infocenter/systems/topic/director.storage_6.1/
fqm0_r_panel_create_volume_page.html): The description of the Volume prefix
field in the Fields section has changed. 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.

What’s new in version 6.1 xxix

 v “Command Automation page”
(publib.boulder.ibm.com/infocenter/systems/topic/director.status_6.1/
fqm0_r_panel_command_automation.html): A note was added to this topic
stating that using the command automation task to launch interactive programs,
for example notepad.exe, is not supported.
v “Threshold page”
(publib.boulder.ibm.com/infocenter/systems/topic/director.status_6.1/
fqm0_r_panel_activate_edit_thresholds.html): This topic has been updated to
include the following note with the ″Resend delay″ definition:

Note: Other than zero, the minimum polling time on the server is five seconds.
So, if you specify a resend value between (but not including) 0 and 5 seconds,
the server will automatically resend events only once every five seconds.
v “Process Management page: Applications page”
(publib.boulder.ibm.com/infocenter/systems/topic/director.status_6.1/
fqm0_r_process_management_window_applications_page.html): The following
option and associated text has been removed from this topic:
Monitors → Process Monitors
Displays the Process Monitors page, which you can use to define a
monitor or an event threshold for a specified process.
v “Process Management page: Services page”
(publib.boulder.ibm.com/infocenter/systems/topic/director.status_6.1/
fqm0_r_process_management_window_services_page.html): The following
option and associated text has been removed from this topic:
Monitors → Process Monitors
Displays the Process Monitors page, which you can use to define a
monitor or an event threshold for a specified process.
v “Process Management page: Device Services page”
(publib.boulder.ibm.com/infocenter/systems/topic/director.status_6.1/
fqm0_r_process_management_window_device_services_page.html): The
following option and associated text has been removed from this topic:
Monitors → Process Monitors
Displays the Process Monitors page, which you can use to define a
monitor or an event threshold for a specified process.
v “Process Management page: Subsystems page”
(publib.boulder.ibm.com/infocenter/systems/topic/director.status_6.1/
fqm0_r_process_management_window_subsystems_page.html): The following
option and associated text has been removed from this topic:
Monitors → Process Monitors
Displays the Process Monitors page, which you can use to define a
monitor or an event threshold for a specified process.
v “Process Management page: Servers page”
(publib.boulder.ibm.com/infocenter/systems/topic/director.status_6.1/
fqm0_r_process_management_window_servers_page.html): The following
option and associated text has been removed from this topic:
Monitors → Process Monitors
Displays the Process Monitors page, which you can use to define a
monitor or an event threshold for a specified process.
v “SNMP Browser page”
(publib.boulder.ibm.com/infocenter/systems/topic/director.status_6.1/
fqm0_r_panel_snmpb_snmp_browser_window.html): In this topic, the section

xxx IBMSystems Director Systems Management Guide

 about right-click options has been removed and topic, and the introduction
paragraph has been updated to to remove mention of setting community names
and attributes.
v “SNMP Management page”
(publib.boulder.ibm.com/infocenter/systems/topic/director.status_6.1/
fqm0_r_panel_snmpb_snmp_browser_page.html): Mention of setting
community names and attributes in the description for the ″SNMP Browser″
action has been removed from this topic.
v “Configure Access page”
(publib.boulder.ibm.com/infocenter/systems/topic/director.security_6.1/
fqm0_r_panel_basic_configure_access.html): The following option has been
added to this topic:
Apply Credentials
Initiates the process of authenticating credentials that are currently
configured on remote access points to the target resource.

Terminology changes
Several terms have changed in IBM Systems Director V6.1.

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; additional 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

What’s new in version 6.1 xxxi

 Deprecated terms New terms Description
Level-0 managed Agentless-managed A system that does not have an agent
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
operating system and hardware: discover
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
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 additional function.
Job activation Job instance A specific occurrence of a job that is
running or has completed running.
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,
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 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.

xxxii IBMSystems Director Systems Management Guide

Chapter 1. Overview of IBM Systems Director
This section provides an overview of IBM Systems Director, including release
notes, 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.

License information
Before deploying this product, ensure that you have the necessary licenses.

IBM Systems Director

IBM Systems Director contains management server and agent components, and
you are authorized to use the components on IBM® systems. You are not
authorized to run IBM Systems Director Server on non-IBM® systems.

You are authorized to manage non-IBM® systems that run Platform Agent and
non-IBM® systems without an agent. See the hardware and software requirements
for more information about supported systems.

You are authorized to use management server and agent components only on
IBM® systems. Notwithstanding the foregoing, the IBM Systems Director 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® systems and install
IBM Systems Director on only one of them, you are entitled to install the agent
component on only 20 non-IBM® x86 systems. If you install IBM Systems Director
on both IBM® systems, 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®. You can purchase
licenses from the Ready to Buy Web Page at www.ibm.com/systems/
management/director/buy/

IBM® may audit your compliance with these terms upon reasonable advance notice
to you.

Database

IBM Systems Director Server uses a database to store data. You can use the Apache
Derby database that is included with IBM Systems Director without obtaining
additional licenses. If you choose to install and use a different supported database,
ensure that you have obtained any required license for the installation.

© Copyright IBM Corp. 1999, 2009 1

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.

Through a single user interface, IBM Systems Director provides consistent views
for viewing managed systems, determining how these systems relate to one
another, and identifying their statuses, thus helping to correlate technical resources
with business needs. A set of common tasks included with IBM Systems Director
provides many of the core capabilities required for basic management, which
means instant out-of-the-box business value. These common tasks include
discovery, inventory, configuration, system health, monitoring, updates, event
notification and automation across managed systems.

IBM Systems Director’s Web and command-line interfaces provide a consistent

interface 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 a variety of IBM® and non-IBM® hardware driving
common tasks through the following platform management plug-ins and virtual
resources. The systems supported include:
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 and System x management
– IBM BladeCenter chassis components, such as switch modules and server
blades
– System x systems and blade servers
– VMWare, Microsoft Virtual Server (MSVS), and Xen virtual 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)

2 IBMSystems Director Systems Management Guide

 – Network storage, such as DS3000, DS4000, and DS6000™
– Storage switches, such as IBM BladeCenter SAS, Brocade, Qlogic, Nortel and
Cisco

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.

Chapter 1. Overview 3
 Management server

IBM Systems Director Server installed

Includes:
- IBM Systems Director Server
- IBM Systems Director Web interface
- Command-line Interface
- Common Agent

HTTPS TCP/IP Various protocols

Browser system SNMP devices

- no IBM Systems Director
Ccode installed
Agentless managed systems Agentless managed systems
- no IBM Systems Director - no IBM Systems Director
Ccode installed Ccode installed
Cco

Platform managed systems

- Platform Agent installed
on each

Common managed systems

- Common Agent installed
on each

FQM0501-0

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, Apache Derby,
although you can choose to use any supported database (including the
high-performance DB2® 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.

4 IBMSystems Director Systems Management Guide

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 IBM® Power Systems, IBM® System x, IBM
BladeCenter, IBM® System z systems, and some non-IBM® systems, when the
system is running a supported operating system.

Notes:
v Systems running AIX require the 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 supports systems running Level 2: Common Agent and IBM Director
Agent version 5.20.

Common Agent has a single run-time that can be shared by IBM Systems Director
and Tivoli products, such as Tivoli Provisioning Manager, to reduce the agent
footprint, support shared credentials, and drive common services. It is also
supported by other management products that use the IBM Tivoli Common Agent
Services management infrastructure version 1.4.1 or later.

The function available for Common-Agent managed systems varies based on

operating system and hardware, and includes:
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, reducing the demands on
IBM Systems Director Server. Firewall management is simplified, too, because the
Common Agent requires you to keep fewer ports open.

For a detailed list of function 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

Chapter 1. Overview 5
 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 and are distributed by other management products such as Tivoli
Provisioning Manager. When referring to these common agents generically,
lowercase text is used.

Platform Agent
Platform Agent is well 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 Universal Manageability Enablement

(UME) in the base operating system.

Platform Agent is equivalent to Level 1: IBM Director Core Services version 5.20.3.
IBM Systems Director supports systems running IBM Director Core Services
version 5.20.3.

Note: The versioning for Platform Agent might not match the versioning of IBM
Systems Director.

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 very 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.

6 IBMSystems Director Systems Management Guide

 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 well suited for one-time collection of inventory,

and can be used for updating firmware and drivers, and remotely deploying and
running it via 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 and hardware.
v Discover systems
v Collect limited operating-system inventory data
v Remotely deploy and install Common Agent and Platform Agent.
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 information in the information center at.

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 and
use the Navigate Resources task to view and work with these resources.

Manageable systems
A system is one type of resource that IBM Systems Director manages. It is an
operating-system-based or hardware-based endpoint that has an IP address and
host name and can be discovered and managed by IBM Systems Director. From the
Navigate Resource page in Web interface, you can view the All Systems group to
work with all discovered systems.

Operating-system-based systems (referred to as operating systems) consist of the

operating system image, agent, drivers, applications, and configuration settings.
From the Navigate Resource page in Web interface, you can view the All Operating
Systems group to work with these types of 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 Navigate Resource page in Web interface, you
can use the All Systems or Virtualization 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. You can also use the topology map to view the relationship between
systems. To view the topology map view for a system, click Actions > Topology
Perspectives. A submenu of applicable perspectives is displayed.

To view resources associated with a system, click Actions > Related Resources. A
submenu of applicable related resources is displayed.

IBM Systems Director manages these types of systems:

Chapter 1. Overview 7
 v Blade administrative server
v Boot server
v Cluster
v Fabric
v Farm
v Generic system
v Hardware Management Console
v Management controller
v Operating system
v Print server
v SAN
v Server
v Storage system
v Switch
v System chassis

Virtualization allows you to 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 into 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 using this 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.

8 IBMSystems Director Systems Management Guide

 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.
v The IBM Systems Director Launched Tasks program is displayed and opens the
task that you selected.

IBM Systems Director provides some tasks that still require a client-based
application. This application is called the IBM Systems Director Launched Tasks
program. The IBM Systems Director Launched Tasks program can open the
following tasks:
v Event Action Editor (used to create advanced event actions)
v Event Filter Builder (used to create advanced event filters)
v File Transfer
v Command Automation (formerly called Process Management - Tasks)
v Remote Session
v SNMP Browser
v MIB Management

Note: The IBM Systems Director Launched Tasks program is installed

automatically the first time you use a task that requires it. Because the IBM
Systems Director Launched Tasks program opens outside of the IBM Systems
Director Web interface, Java™ Web Start (JWS) is also provided for installation. For
more information, see “Downloading Java Web Start.”

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 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:

Chapter 1. Overview 9
 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
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 agents on new systems, upgrading from IBM Director Agent version
5.20 or IBM Director Core Services version 5.20 to a current agent on existing
systems, and promote an Agentless-managed system or Platform-Agent
managed system to a Common-Agent managed system.

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 such as physical and virtual servers, storage systems, and
network devices) in a heterogeneous environment. This includes simple
discovery using a single IP address or host name or a range of IP addresses. You
can also use a discovery profile to discover one or more systems of different
types and protocols.
v Collect inventory data about hardware and software that is currently 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
using the Resource Navigator
v Pass security credentials to one or more systems to gain access to that agents

Status manager
Status manager provides an at-a-glance view of the health of your managed
resources (including systems, operating systems, applications, and security) and
processes.

The status of discovered systems is automatically retrieved and displayed, and this
display can be customized in several ways—using one of the system health and
status-related tasks, navigating to a specific resource, or using the new capabilities
integrated into the command line interface.

10 IBMSystems Director Systems Management Guide

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 will help you manage the status, problems and
events for systems.
v Determine the health, compliance, and performance of managed systems in your
environment 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 metrics for specific
managed systems.
v View the event log.
v Identify problems and find the root cause by viewing problems and the event
log.
v Subscribe to events on the ones deemed important. You can also identify events
to be cleared automatically.
v Monitor dynamic properties of resources by defining monitors and thresholds
and generating a notification when a threshold has been reached.
v Monitor processes and device services on a specific system by defining monitors
and thresholds and generating a notification when a threshold has been reached.
v Monitor system information in various formats.
v Drill down into the root cause of problems.

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 leverages a set of well defined templates that
can be applied to servers, storage, and network resources even if the resources are
comprised of very 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 will 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 using the automatic-deploy
capability of a configuration plan.
v Reconfigure systems to prepare for redeployment, reallocation, or
re-provisioning (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
tasks 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 will help you automate tasks.

Chapter 1. Overview 11
 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. The types of 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 notifications 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 will 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 tin a single
request without repackaging or performing each step in the process separately.
v Download and review update information, such as prerequisites, readmes,
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 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 Run hardware management commands from the hardware command line, which
connects to the service processor of the target system.
v Transfer files from one location to another and synchronizing files, directories, or
drives using a secure alternative to FTP.
v Open console windows to one or more POWER managed systems.
v Execute a command on one or more managed systems in parallel.

Virtualization manager
Virtualization manager provides tools for managing the lifecycle of virtual
resources.

12 IBMSystems Director Systems Management Guide

Virtualization manager now includes support for virtualized environments
managed by wholly different server virtualization environments. These include
Hardware Management Console (HMC), Integrated Virtualization Manager (IVM),
Microsoft Virtual Server, VMware and Xen virtualization. Some additional basic
discovery and health management is supported for z/VM virtualization. As a
result of this cross-solution management consolidation, you can visualize and
control both the physical and virtual resources from a single user interface.

You can use the virtualization manager plug-in to:

v Work with virtualized environments and tools, including Hardware
Management Console (HMC), Integrated Virtualization Manager (IVM),
Microsoft Virtual Server, VMware, and Xen virtualization
v Viewing topology that shows the connections between physical and virtual
resources, which can vary dynamically across time
v Tracking alerts and system status for virtual resources and their resources to
easily diagnose problems affecting virtual resources
v Creating automation plans based on events and actions from virtual and
physical resources, such as relocating a virtual server based on critical hardware
alerts
v Create, delete and manage virtual servers and virtual farms for several
virtualization technologies in the industry
v Relocate virtual servers to alternate physical hosts

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.

IBM BladeCenter and System x management

IBM BladeCenter and System x management provides lifecycle management of
your modular System x and IBM BladeCenter systems and related resources,
including discovery, health and status monitoring, configuration, updates, and
virtualization. It also provides platform-specific functions.

You can use the IBM BladeCenter and System x management plug-in to:
v Change power settings
v Manage hardware logs
v Identify hardware using the locator LED
v Turn off 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 used in the Welcome panel
summary view and includes support for Linux on System z and z/VM systems
running on IBM® System z mainframes.

Chapter 1. Overview 13
 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 System environments that might include
POWER5™ and POWER6™ processor-based servers 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 AIX 6.1 and IBM i 5.4 and 6.1.

For additional information about managing the virtualization and consolidation on

Power systems using IBM Systems Director, see the Managing IBM Power Servers
with IBM Systems Director 6.1 white paper on the Web at: www.ibm.com/
common/ssi/fcgi-bin/ssialias?infotype=SA&subtype=WH
&appname=STGE_PO_PO_USEN&htmlfid=POW03011USEN
&attachment=POW03011USEN.PDF

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 Launch storage management applications
v Use integrated SCM features to manage integrated RAID Controllers,
BladeCenter SAS modules, and BC-S RAID SAS modules
v Use embedded management interfaces for DS3000, DS4000, and DS6000, and
TotalStorage Productivity Center (TPC) to manage SAN Volume Controller
(SVC), DS8000® and ESS 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 tailored to a
particular environment.

14 IBMSystems Director Systems Management Guide

 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 Web site at
www.ibm.com/systems/management/director/plugins/.

Active Energy Manager plug-in

The Active Energy Manager plug-in helps you to manage, monitor and collect
energy-consumption data from IBM® systems including IBM BladeCenter chassis
and rack-mounted System x servers. You can use Active Energy Manager to:
v Allocate less power and cooling infrastructure to your IBM® servers.
v Lower 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 for-fee licensed plug-in that supports Windows, Linux
for x86, and Linux for Power platforms.

BladeCenter Open Fabric Manager plug-in

The BladeCenter Open Fabric Manager plug-in helps you to quickly replace and
recover blades in your environment. You can use this plug-in to:
v Pre-assign MAC and WWN addresses, as well as storage boot targets for up to
100 chassis or 1400 blade servers.
v Create addresses for blade servers, save the addresses to a configuration file, and
deploy the addresses to the blade slots in the same chassis or in up to 100
different chassis without any blade servers installed in the chassis.
v Automatically replace a failed blade from a designated pool of spare blades.

BladeCenter Open Fabric Manager is a for-fee plug-in that supports all platforms
that IBM Systems Director supports.

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 the 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 using encryption
and authentication.

Service and Support Manager is a free plug-in that supports Windows and Linux
for x86 platforms.

Upward integration
IBM Systems Director lets you to make the most of your existing enterprise
management structure by upwardly integrating with many workgroup and
enterprise-management products.

Chapter 1. Overview 15
 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 in the IBM Systems information center on
the Web at publib.boulder.ibm.com/infocenter/systems/topic/uims/
fqs0_main.html.

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.

I’m a 5.20 user. How do I use 6.1?

You know what you need to do in IBM Director 5.20, now use this section to learn
how to do it in IBM Systems Director 6.1. After you become accustomed to this
interface, you’ll be able to see the status of your systems management environment
quickly and more easily than ever before.

Meeting customer demand for a Web-based interface, IBM Systems Director 6.1
delivers cutting-edge usability built on industry-accepted Web-interface standards.

Use these topics to find answers to some of the questions you might have about
IBM Systems Director 6.1.

Why am I starting at the Welcome page?

In IBM Director Console version 5.20, limited status information was displayed
along the bottom of the window. This information included the number of
managed objects that had critical, warning, or information alerts; the status of IBM
Director; the host and login information for IBM Director Server; and the number
of managed objects in the Group Contents pane. In the IBM Systems Director Web
interface, the Welcome page gives you at-a-glance status information.

16 IBMSystems Director Systems Management Guide

 The Welcome page gives you information about all of your systems with fast-path
options to detailed information and tasks. The Welcome page lets you start your
work with a clear picture of your current systems-management environment.

IBM Systems Director Welcome page

Use the IBM Systems Director Welcome page to complete 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 to
expand your skills with IBM Systems Director.

Figure 2. The Welcome page displaying the Start, Manage, and Learn tabs

The following links are available at the top of the Welcome page:

Find a resource
Provides a way to quickly and easily find one or more resources in your
systems-management environment.

Find a task
Provides a way to quickly and easily find any task in IBM Systems
Director.

I’m a 5.20 user; how do I use 6.1?

Opens the IBM Systems Director information center to provide information
that describes how to use IBM Systems Director 6.1.0 compared to the
tasks in IBM Director version 5.20. This information is specifically designed
for IBM Director version 5.20 users that want to understand how to
complete familiar tasks using the new IBM Systems Director Web interface.

About
Displays the version of your IBM Systems Director installation.

Web resources
Displays other information resources that are available on the Web.

View updates
Checks for and displays any updates that are available from the IBM® Web
site that are required by IBM Systems Director Server.

Chapter 1. Overview 17
 Related concepts
“System severity states” on page 88
Related tasks
“Starting work in IBM Systems Director” on page 24
“Learning about the product” on page 28
“Checking IBM Systems Director readiness” on page 25
“Viewing updates” on page 28
“Viewing tutorials” on page 29
“Viewing the IBM Systems Director Server summary” on page 26

The Start page:

Provides the tasks to perform initial discovery in your systems-management

environment, request access to your discovered resources, and collect inventory
from your resources. Then, use the next steps provided on this page to make IBM
Systems Director more productive. A user must have the AllPermission permission
to view this page; otherwise, it is not displayed. For more information, see
“Security.”

18 IBMSystems Director Systems Management Guide

Figure 3. The Welcome page interface displaying the Start page

Getting Started
Provides tasks and information that you can use to get started with IBM
Systems Director.

Chapter 1. Overview 19
 Discover
Performs initial discovery in your systems-management environment. This
discovery method searches the entire subnet of the server on which IBM
Systems Director Server is installed. It utilizes all the protocols that IBM
Systems Director uses to discover systems.

Status chart
Provides status information about resources that IBM Systems Director has
discovered. This information includes the number of operating systems
that are managed by way of the Common Agent, Platform Agent, or no
agent; the number of systems to which you do not have access, and the
number of systems on which inventory has not been collected. Click any of
these links to display detailed information about the affected systems and
resources.

Optional tasks
Provides optional tasks for getting started including the discovery,
inventory, and navigate resources.

Next Steps
Provides typical tasks for setting up IBM Systems Director, including
registering with IBM®, creating thresholds and event automation plans,
checking for updates, installing Common Agent on systems, setting up
security, and configuring your systems.
Related concepts
The Manage page
The Learn page
Related tasks
“Performing initial discovery” on page 235

The Manage page:

Provides information that you can use to determine whether IBM Systems Director
and its plug-ins are ready to use. 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. After the initial discovery is completed, the
Manage page is displayed by default when you view the Welcome page.

The Manage tab includes an icon that is displayed if any problems exist with one
or more plug-ins.

Note: The Manage page displays only the plug-ins that the user is authorized to
use. If a user is not authorized to use any plug-ins, the Manage page is not
displayed.

20 IBMSystems Director Systems Management Guide

Figure 4. The Manage tab with the Information icon

The icon displayed is tied to the plug-in states that are displayed on the Manage
page:

If one or more plug-ins are in an Error state, the Error-connecting icon is

displayed on the Manage tab.

If one or more plug-ins are in the Setup-required state, the Setup-required

icon is displayed on the Manage tab.
No icon

If all plug-ins are in the ready state or collecting-data state ,

then no icon is displayed on the Manage tab.

Chapter 1. Overview 21
Figure 5. The Welcome page interface displaying the Manage page

22 IBMSystems Director Systems Management Guide

 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.
Related concepts
The Start page
The Learn page

The Learn page:

Provides a list of available tutorial links. Each 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.

Chapter 1. Overview 23
Figure 6. The Welcome page interface displaying the Learn page

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 Start page
The Manage page

Starting work in IBM Systems Director

Before IBM Systems Director can manage your systems, the systems must be
discovered. Using the Welcome 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 Welcome page is
displayed automatically. Otherwise, in the IBM Systems Director navigation
area, click Welcome.
2. On the IBM Systems Director Welcome page, view the Getting Started section
on the Start page. This section provides status information about resources that
IBM Systems Director has discovered. This information includes the number of
operating systems that are managed by way of the Common Agent, Platform
Agent, or no agent; the number of systems to which you do not have access,

24 IBMSystems Director Systems Management Guide

 and the number of systems on which inventory has not been collected. Click
any of these links to display detailed information about the affected systems
and resources.

Note: If you have not performed discovery yet, discovery and system access
information is reported only for the management server.
In the Optional tasks area, the tasks that are commonly used when setting up
IBM Systems Director are provided.
3. View the Next Steps section on the Start page. This section provides typical
tasks for setting up IBM Systems Director, including registering with IBM®,
creating thresholds and event automation plans, checking for updates, installing
Common Agent on systems, setting up security, and configuring your systems.
Related concepts
IBM Systems Director Welcome page
“System severity states” on page 88
Learning and tutorials
Related tasks
“Learning about the product” on page 28
“Checking IBM Systems Director readiness”
“Viewing updates” on page 28
“Viewing tutorials” on page 29
“Viewing the IBM Systems Director Server summary” on page 26
Related reference
All possible ports

Checking IBM Systems Director readiness

You can determine whether the plug-ins in your IBM Systems Director installation
are ready for use by viewing the Welcome page.

To determine whether plug-ins are ready for use, complete the following steps:
1. In the IBM Systems Director navigation area, click Welcome.
2. On the Welcome page, click the Manage tab.
3. Browse the Manage 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.

Chapter 1. Overview 25
 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 Manage 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
IBM Systems Director Welcome page
“System severity states” on page 88
Learning and tutorials
Related tasks
“Starting work in IBM Systems Director” on page 24
“Learning about the product” on page 28
“Viewing updates” on page 28
“Viewing tutorials” on page 29
“Viewing the IBM Systems Director Server summary”
Related reference
All possible ports

Viewing the IBM Systems Director Server summary

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:
1. In the IBM Systems Director navigation area, click Welcome.
2. On the Welcome page, click the Manage tab.
3. On the Welcome page, 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.

26 IBMSystems Director Systems Management Guide

 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 Current management server statistics: 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 at a specific network
address or range of addresses.
Advanced system discovery
Click Advanced system discovery to discover a specific type of
resource or schedule a discovery task.
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.
Navigate resources
Click Navigate Resources 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.
v In the Common tasks area, the following links are provided:
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.”

Chapter 1. Overview 27
 Related concepts
IBM Systems Director Welcome page
“System severity states” on page 88
Learning and tutorials
Related tasks
“Starting work in IBM Systems Director” on page 24
“Learning about the product”
“Checking IBM Systems Director readiness” on page 25
“Viewing updates”
“Viewing tutorials” on page 29
“Finding systems and other resources” on page 61
“Finding a task” on page 162
Related reference
All possible ports

Learning about the product

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 Welcome. On the Welcome
page, click the Learn tab. View the available tutorials to expand your skills with
IBM Systems Director.
v On the Welcome page, click the Manage 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/systems/topic/director_6.1/fqm0_main.html 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
IBM Systems Director Welcome page
“System severity states” on page 88
Learning and tutorials
Related tasks
“Starting work in IBM Systems Director” on page 24
“Checking IBM Systems Director readiness” on page 25
“Viewing updates”
“Viewing tutorials” on page 29
“Viewing the IBM Systems Director Server summary” on page 26

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 Welcome to
view the Welcome page and complete any of the following steps:

28 IBMSystems Director Systems Management Guide

v On the Welcome page, in the upper right-corner, click View updates. The View
Updates page is displayed.
v On the Start page, in the Next Steps section, click Check for updates on
discovered systems.
1. On the Check for Updates page, select the types of updates for which you
want check and click OK. Using the Check for Updates page, you can start
managing updates in the following ways:
– Select the systems to keep in compliance with the latest updates.
– Create an update group to contain the updates for your selected systems.
– Configure a connection to the Internet.
– Run or schedule a check for updates.
2. In the Run - Check for Updates window, click OK to start Check for Updates
immediately. IBM Systems Director checks for any updates that are available
from the IBM® Web site. A message is displayed stating that the Check for
Updates has run.
3. Click Show Updates. The Show Updates page is displayed.
v On the Welcome page, click the Manage tab. On the Manage page, view the
Update Manager section and click Check for Updates. The Check for Updates
page described in the preceding step is displayed.
Related concepts
IBM Systems Director Welcome page
“System severity states” on page 88
Learning and tutorials
Related tasks
“Starting work in IBM Systems Director” on page 24
“Learning about the product” on page 28
“Checking IBM Systems Director readiness” on page 25
“Viewing tutorials”
“Viewing the IBM Systems Director Server summary” on page 26
Related reference
All possible ports

Viewing tutorials
You can view tutorials to learn quickly how to use tasks and feature provided by
IBM Systems Director.

To view tutorials, complete the following steps:

1. In the IBM Systems Director navigation area, click Welcome.
2. On the Welcome page, click the Learn tab. The Learn page 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.”

Chapter 1. Overview 29
 Related concepts
IBM Systems Director Welcome page
“System severity states” on page 88
Learning and tutorials
Related tasks
“Starting work in IBM Systems Director” on page 24
“Learning about the product” on page 28
“Checking IBM Systems Director readiness” on page 25
“Viewing updates” on page 28
“Viewing the IBM Systems Director Server summary” on page 26
Related reference
All possible ports

What can I do with the rest of the interface?

In the IBM Systems Director Web interface, the Welcome page is displayed in the
content area. The navigation area provides commonly used tasks at the top, along
with controls to customize the Web interface for your specific needs.

30 IBMSystems Director Systems Management Guide

Figure 7. 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 Navigate
Resources, Inventory, Health Summary, and Automation and Settings.

Content area
When you open the Web interface, by default you see the Welcome 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.”

View list
In the navigation area, this list provides the following alternate view
selections:

Chapter 1. Overview 31
 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.”
IBM Systems Director
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.

How do I discover my systems?

In IBM Director Console version 5.20 you could manually discover an individual
system, or use discovery preferences. In the IBM Systems Director Web interface,
you can perform an initial discovery of your subnet from the Start page on the
Welcome page.

From the Start page, you can also link to tasks to discover individual systems as
well as create discovery profiles for advanced system discovery. Alternatively, these
tasks are available from the Inventory section of the navigation area.

Performing a system discovery

Use the System Discovery task to identify systems at a specific network address or
range of addresses.

To perform a system discovery, complete the following steps:

1. Open the System Discovery page using either of these two methods:
v On the Welcome page, click System discovery under Optional tasks.
v In the IBM Systems Director Web interface navigation area, expand
Inventory and then click System Discovery.
The System Discovery page is displayed.

32 IBMSystems Director Systems Management Guide

2. Select one of the following discovery methods:
Table 3. System discovery methods
To do this task:
Add a single IP address
Add a range of IP addresses
Add a host name of a system
Complete these steps:
1. Click Single system (IP address).
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
resource type list.
1. Click Multiple systems (Range of IP
addresses).
2. For the IP address range that contains
the systems that you want to discover,
type the low-end IP address value in the
Starting IP address field and the
high-end IP address value in the Ending
IP address field.
3. If you want to discover only a specific
resource type, select it from the Select
resource type list.
1. Click Single system (Hostname).
2. In the Hostname field, type the host
name of the system that you want to
discover.
3. If you want to discover only a specific
resource type, select it from the Select
resource type list.

3. Click Discover. The Processing discovery protocols message is displayed and

the progress of the discovery process is displayed as a spinning graphic.

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.
4. Optional: If you want to stop the discovery process, click Stop during
discovery.

As systems are discovered, they are displayed in the Discovered Systems table.

Note: After a resource is discovered, the virtual systems that are associated with
that resource are also discovered.

Chapter 1. Overview 33
 Related concepts
“Discovery” on page 231
“Discovery protocols” on page 232
“System discovery” on page 237
“Inventory data and collection profiles” on page 259
Related tasks
“Accessing a secured system with request access” on page 714
“Discovering and collecting inventory for storage devices” on page 590
“Collecting inventory” on page 68

Creating a discovery profile

From the Advanced System Discovery page, you can create a discovery profile.

To create a discovery profile, complete the following steps:

1. Open the Advanced System Discovery page using either of these two
methods:
v On the Welcome page, click Advanced System Discovery under Optional
tasks.
v In the IBM Systems Director Web interface navigation area, expand
Inventory and then click Advanced System Discovery.
2. On the Advanced System Discovery page, click Create. The Advanced
Discovery Wizard opens and the Welcome page is displayed.
3. Optional: To prevent the Welcome page from displaying the next time you
create a profile, clear Show this Welcome page next time.
4. Click Next. The Profile properties page is displayed.
5. In the Profile name field, type a descriptive name for the profile.
6. From the System type list, select the type of resource that you want to
discover with the profile. The protocols that are available on the next page of
the Advanced Discovery Wizard depend on which profile type is selected
here.
7. Optional: If you want to provide further granularity to your discovery search,
use the System subtype list to select a subtype for the system type that you
previously selected. The default system subtype is All, which will discover all
system subtypes for the selected system type.

Note: The list of system subtypes is dynamically populated based on which

system type you choose.
8. In the Profile description field, type a brief description for the profile.
9. Click Next. The Protocol Selection page is displayed.
10. Select the protocols that you want to use for the discovery profile.

Note: When the profile is run, IBM Systems Director Server uses only the
communication protocols that are saved in the profile. When a profile that
contains multiple protocols is run, the management server sends an IP packet
for each protocol in the profile to every resource that is targeted, which
increases network traffic.
11. Click Next. Complete all pages for each protocol that you selected, clicking
Next on each page to navigate to the next page. Details for each protocol are
as follows:

34 IBMSystems Director Systems Management Guide

Agent manager configuration
Select individual agent managers or choose to use all available agent
managers with your profile.
Selecting individual agent managers
In the list of agent managers, select the ones that you want to
use for discovery.
Selecting all available agent managers
Select the Use all available agent managers when this profile
is run. option.
Common Agent Services (CAS) configuration
Configure either unicast, multicast and broadcast, or directory agents
to discover your resources. Also activate or deactivate access request
automation and activate or deactivate inventory discovery automation.

Attention: All three discovery methods (unicast, multicast and

broadcast, and directory agents) are presented on this page and you
can provide information for all three at once. However, only one
method at a time will be used to discover resources. For example, if
you fill in all three sections, only the unicast discovery is performed.
The priority for discovery method processing is as follows:
a. Unicast
b. Directory agents
c. Multicast and broadcast
So, if you want to use multiple methods to discover resources, you
must fill out one section, discover those resources, and then return to
fill out another section and discover those other resources.

Note: You cannot configure directory agents for the following profile
types:
v Hardware management console
v Management controller
v Server, when discovering an IVM
Therefore, ensure that you configure multicast and broadcast if you
choose any of those profile types.
When configuring CAS IP addresses, you can add IP addresses either
individually or as a range, or you can import the addresses.
Adding a single IP address
a. Select Add a single IP address.
b. In the Single IP address or beginning range field, type the
IP address of the resource that you want to discover.
c. Click Add to add the IP address to the list.
d. Repeat this procedure until you have added all the IP
addresses.
Adding a range of IP addresses
a. Select Add a range of IP addresses.
b. For the IP address range that contains the resources that
you want to discover, type the low-end IP address value in
the Single IP address or beginning range field and the
high-end IP address value in the Ending range field.
c. Click Add to add the IP addresses to the list.

Chapter 1. Overview 35
 d. Repeat this procedure until you have added all the IP
addresses.
Importing IP addresses
a. Select Import.
b. In the Select the file that you want to import field, type in
the name of the import file or click Browse to search for
the file.

Note: Ensure that the file you use is a line delimited file
with one IP address on each line.
c. Click OK to import the IP addresses.
When configuring multicast and broadcast, select to enable either and
set the timeout period.
Enabling multicast
Select Enable multicast to enable multicast.
Setting the timeout period
In the Timeout period (seconds) field, select the number of
seconds that the server will wait until timing out.
Enabling general broadcast
Select Enable general broadcast to enable general broadcast.
When configuring directory agents, specify either an IP address or a
host name and set the scope.
Adding a directory agent using its IP address
a. Select Add IP address.
b. In the IP address field, type the IP address of the directory
agent that you want to discover.
c. Click Add to add the IP address to the list.
d. Repeat this procedure until you have added all the IP
addresses.
Adding a directory agent using its host name
a. Select Add host name.
b. In the Host name field, type the host name of the directory
agent that you want to discover.
c. Click Add to add the host name to the list.
d. Repeat this procedure until you have added all the host
names.
Setting the scope
Each directory agent is associated with a scope. A discovery
request is targeted to find only those directory agents that are
associated with the specified scope. The directory agent
shipped with IBM Systems Director has a default scope of
DEFAULT, so that is the default scope value used when
searching for directory agents. If you want to search for
directory agents with scopes other than DEFAULT, complete
the following steps:
a. In the Scope field, type the name of a scope that you have
defined.
b. Click Add to add the scope to the list.
c. Repeat this procedure until you have added all the scopes.
When setting access request automation, you can choose to deactivate
or activate (with the appropriate login information) the feature.

36 IBMSystems Director Systems Management Guide

 Activating access request automation
a. Select Activate - use the following user login information.
b. In the User ID field, type a valid user ID for the resource.
c. In the Password field, type the password for the user ID.
Deactivating access request automation
a. Select Deactivate.
When setting inventory discovery automation, you can choose to
deactivate or activate (with an associated inventory profile) the
feature.
Activating inventory discovery automation
a. Select Activate - use the following inventory profile.
b. In the Inventory profiles list, select the profile that you
want to use for automatic inventory discovery.
Deactivating inventory discovery automation
a. Select Deactivate.
Common Information Model (CIM) configuration
Configure either unicast, multicast and broadcast, or directory agents
to discover your resources. Also activate or deactivate access request
automation and activate or deactivate inventory discovery automation.

Attention: All three discovery methods (unicast, multicast and

broadcast, and directory agents) are presented on this page and you
can provide information for all three at once. However, only one
method at a time will be used to discover resources. For example, if
you fill in all three sections, only the unicast discovery is performed.
The priority for discovery method processing is as follows:
a. Unicast
b. Directory agents
c. Multicast and broadcast
So, if you want to use multiple methods to discover resources, you
must fill out one section, discover those resources, and then return to
fill out another section and discover those other resources.

Note: You cannot configure directory agents for the following profile
types:
v Hardware management console
v Management controller
v Server, when discovering an IVM
Therefore, ensure that you configure multicast and broadcast if you
choose any of those profile types.
When configuring CIM IP addresses, you can add IP addresses either
individually or as a range, or you can import the addresses.
Adding a single IP address
a. Select Add a single IP address.
b. In the Single IP address or beginning range field, type the
IP address of the resource that you want to discover.
c. Click Add to add the IP address to the list.
d. Repeat this procedure until you have added all the IP
addresses.

Chapter 1. Overview 37
 Adding a range of IP addresses
a. Select Add a range of IP addresses.
b. For the IP address range that contains the resources that
you want to discover, type the low-end IP address value in
the Single IP address or beginning range field and the
high-end IP address value in the Ending range field.
c. Click Add to add the IP addresses to the list.
d. Repeat this procedure until you have added all the IP
addresses.
Importing IP addresses
a. Select Import.
b. In the Select the file that you want to import field, type in
the name of the import file or click Browse to search for
the file.

Note: Ensure that the file you use is a line delimited file
with one IP address on each line.
c. Click OK to import the IP addresses.
When configuring multicast and broadcast, select to enable either and
set the timeout period.
Enabling multicast
Select Enable multicast to enable multicast.
Setting the timeout period
In the Timeout period (seconds) field, select the number of
seconds that the server will wait until timing out.
Enabling general broadcast
Select Enable general broadcast to enable general broadcast.
When configuring directory agents, specify either an IP address or a
host name and set the scope.
Adding a directory agent using its IP address
a. Select Add IP address.
b. In the IP address field, type the IP address of the directory
agent that you want to discover.
c. Click Add to add the IP address to the list.
d. Repeat this procedure until you have added all the IP
addresses.
Adding a directory agent using its host name
a. Select Add host name.
b. In the Host name field, type the host name of the directory
agent that you want to discover.
c. Click Add to add the host name to the list.
d. Repeat this procedure until you have added all the host
names.
Setting the scope
Each directory agent is associated with a scope. A discovery
request is targeted to find only those directory agents that are
associated with the specified scope. The directory agent
shipped with IBM Systems Director has a default scope of
DEFAULT, so that is the default scope value used when

38 IBMSystems Director Systems Management Guide

 searching for directory agents. If you want to search for
directory agents with scopes other than DEFAULT, complete
the following steps:
a. In the Scope field, type the name of a scope that you have
defined.
b. Click Add to add the scope to the list.
c. Repeat this procedure until you have added all the scopes.
When setting access request automation, you can choose to deactivate
or activate (with the appropriate login information) the feature.
Activating access request automation
a. Select Activate - use the following user login information.
b. In the User ID field, type a valid user ID for the resource.
c. In the Password field, type the password for the user ID.
Deactivating access request automation
a. Select Deactivate.
When setting inventory discovery automation, you can choose to
deactivate or activate (with an associated inventory profile) the
feature.
Activating inventory discovery automation
a. Select Activate - use the following inventory profile.
b. In the Inventory profiles list, select the profile that you
want to use for automatic inventory discovery.
Deactivating inventory discovery automation
a. Select Deactivate.
Distributed component object model (DCOM) configuration
Configure DCOM IP addresses, activate or deactivate access request
automation, and activate or deactivate inventory discovery
automation.
When configuring DCOM IP addresses, you can add IP addresses
either individually or as a range, or you can import the addresses.
Adding a single IP address
a. Select Add a single IP address.
b. In the Single IP address or beginning range field, type the
IP address of the resource that you want to discover.
c. Click Add to add the IP address to the list.
d. Repeat this procedure until you have added all the IP
addresses.
Adding a range of IP addresses
a. Select Add a range of IP addresses.
b. For the IP address range that contains the resources that
you want to discover, type the low-end IP address value in
the Single IP address or beginning range field and the
high-end IP address value in the Ending range field.
c. Click Add to add the IP addresses to the list.
d. Repeat this procedure until you have added all the IP
addresses.
Importing IP addresses
a. Select Import.

Chapter 1. Overview 39
 b. In the Select the file that you want to import field, type in
the name of the import file or click Browse to search for
the file.

Note: Ensure that the file you use is a line delimited file
with one IP address on each line.
c. Click OK to import the IP addresses.
When setting access request automation, you can choose to deactivate
or activate (with the appropriate login information) the feature.
Activating access request automation
a. Select Activate - use the following user login information.
b. In the User ID field, type a valid user ID for the resource.
c. In the Password field, type the password for the user ID.
Deactivating access request automation
a. Select Deactivate.
When setting inventory discovery automation, you can choose to
deactivate or activate (with an associated inventory profile) the
feature.
Activating inventory discovery automation
a. Select Activate - use the following inventory profile.
b. In the Inventory profiles list, select the profile that you
want to use for automatic inventory discovery.
Deactivating inventory discovery automation
a. Select Deactivate.
Interprocess Communication (IPC) configuration
Configure either unicast or multicast and broadcast (general or
directed) to discover your resources and then optionally configure
broadcast relays. Also activate or deactivate access request automation
and activate or deactivate inventory discovery automation.

Note: Access request automation and inventory discovery automation

are not supported on IPC, so these options will not be displayed if
you configure only IPC. However, if you configure IPC along with
other protocols that support access request automation and inventory
discovery automation, those options will be displayed but apply to
only the supported protocols. So, for example, even if you supply the
correct credentials during configuration of access request automation,
you will not gain access to IPC discovered resources when the
automatic access request runs. Instead, you need to request access and
collect inventory manually using the tasks provided by IBM Systems
Director.
When configuring unicast, you can add IP addresses either
individually or as a range, or you can import the addresses.
Adding a single IP address
a. Select Add a single IP address.
b. In the Single IP address or beginning range field, type the
IP address of the resource that you want to discover.
c. Click Add to add the IP address to the list.
d. Repeat this procedure until you have added all the IP
addresses.
Adding a range of IP addresses

40 IBMSystems Director Systems Management Guide

 a. Select Add a range of IP addresses.
b. For the IP address range that contains the resources that
you want to discover, type the low-end IP address value in
the Single IP address or beginning range field and the
high-end IP address value in the Ending range field.
c. Click Add to add the IP addresses to the list.
d. Repeat this procedure until you have added all the IP
addresses.
Importing IP addresses
a. Select Import.
b. In the Select the file that you want to import field, type in
the name of the import file or click Browse to search for
the file.

Note: Ensure that the file you use is a line delimited file
with one IP address on each line.
c. Click OK to import the IP addresses.
When configuring multicast and broadcast, select to enable either,
configure them, and set the timeout period.
Enabling multicast
a. Select Enable multicast.
b. In the Multicast IP address field, enter the IP address that
multicast discovery will use.
Setting the timeout period
In the Timeout period (seconds) field, select the number of
seconds that the server will wait until timing out.
Enabling general broadcast
Select Enable general broadcast to enable general broadcast.
Enabling directed broadcast
a. Select Enable directed broadcast.
b. In the IP address field, enter the IP address that directed
broadcast discovery will use.
c. In the Subnet mask field, enter the subnet mask that
directed broadcast discovery will use.
When configuring the relay broadcast option, specify the agent that
will send the broadcast.
Setting an agent to send a broadcast
a. In the IP address field, enter the IP address of the agent.
b. In the Subnet mask field, enter the subnet mask of the
agent.
c. Click Add to add the host name to the Table of relay data
list.
d. Repeat this procedure until you have added all the agents.
e. If you want to not use a particular agent for broadcasting,
select it in the list and click Delete.
Secure shell (ssh) configuration
Configure ssh IP addresses, activate or deactivate access request
automation, and activate or deactivate inventory discovery
automation.

Chapter 1. Overview 41
 When configuring ssh IP addresses, you can add IP addresses either
individually or as a range, or you can import the addresses.
Adding a single IP address
a. Select Add a single IP address.
b. In the Single IP address or beginning range field, type the
IP address of the resource that you want to discover.
c. Click Add to add the IP address to the list.
d. Repeat this procedure until you have added all the IP
addresses.
Adding a range of IP addresses
a. Select Add a range of IP addresses.
b. For the IP address range that contains the resources that
you want to discover, type the low-end IP address value in
the Single IP address or beginning range field and the
high-end IP address value in the Ending range field.
c. Click Add to add the IP addresses to the list.
d. Repeat this procedure until you have added all the IP
addresses.
Importing IP addresses
a. Select Import.
b. In the Select the file that you want to import field, type in
the name of the import file or click Browse to search for
the file.

Note: Ensure that the file you use is a line delimited file
with one IP address on each line.
c. Click OK to import the IP addresses.
When setting access request automation, you can choose to deactivate
or activate (with the appropriate login information) the feature.
Activating access request automation
a. Select Activate - use the following user login information.
b. In the User ID field, type a valid user ID for the resource.
c. In the Password field, type the password for the user ID.
Deactivating access request automation
a. Select Deactivate.
When setting inventory discovery automation, you can choose to
deactivate or activate (with an associated inventory profile) the
feature.
Activating inventory discovery automation
a. Select Activate - use the following inventory profile.
b. In the Inventory profiles list, select the profile that you
want to use for automatic inventory discovery.
Deactivating inventory discovery automation
a. Select Deactivate.
Service Location Protocol (SLP) configuration
Configure either unicast, multicast and broadcast, or directory agents
to discover your resources.

42 IBMSystems Director Systems Management Guide

Attention: All three discovery methods (unicast, multicast and
broadcast, and directory agents) are presented on this page and you
can provide information for all three at once. However, only one
method at a time will be used to discover resources. For example, if
you fill in all three sections, only the unicast discovery is performed.
The priority for discovery method processing is as follows:
a. Unicast
b. Directory agents
c. Multicast and broadcast
So, if you want to use multiple methods to discover resources, you
must fill out one section, discover those resources, and then return to
fill out another section and discover those other resources.

Note: You cannot configure directory agents for the following profile
types:
v Hardware management console
v Management controller
v Server, when discovering an IVM
Therefore, ensure that you configure multicast and broadcast if you
choose any of those profile types.
When configuring unicast, you can add IP addresses either
individually or as a range, or you can import the addresses.
Adding a single IP address
a. Select Add a single IP address.
b. In the Single IP address or beginning range field, type the
IP address of the resource that you want to discover.
c. Click Add to add the IP address to the list.
d. Repeat this procedure until you have added all the IP
addresses.
Adding a range of IP addresses
a. Select Add a range of IP addresses.
b. For the IP address range that contains the resources that
you want to discover, type the low-end IP address value in
the Single IP address or beginning range field and the
high-end IP address value in the Ending range field.
c. Click Add to add the IP addresses to the list.
d. Repeat this procedure until you have added all the IP
addresses.
Importing IP addresses
a. Select Import.
b. In the Select the file that you want to import field, type in
the name of the import file or click Browse to search for
the file.

Note: Ensure that the file you use is a line delimited file
with one IP address on each line.
c. Click OK to import the IP addresses.
When configuring multicast and broadcast, select to enable either and
set the timeout period.

Chapter 1. Overview 43
 Enabling multicast
Select Enable multicast to enable multicast.
Setting the timeout period
In the Timeout period (seconds) field, select the number of
seconds that the server will wait until timing out.
Enabling general broadcast
Select Enable general broadcast to enable general broadcast.
When configuring directory agents, specify either an IP address or a
host name and set the scope.
Adding a directory agent using its IP address
a. Select Add IP address.
b. In the IP address field, type the IP address of the directory
agent that you want to discover.
c. Click Add to add the IP address to the list.
d. Repeat this procedure until you have added all the IP
addresses.
Adding a directory agent using its host name
a. Select Add host name.
b. In the Host name field, type the host name of the directory
agent that you want to discover.
c. Click Add to add the host name to the list.
d. Repeat this procedure until you have added all the host
names.
Setting the scope
Each directory agent is associated with a scope. A discovery
request is targeted to find only those directory agents that are
associated with the specified scope. The directory agent
shipped with IBM Systems Director has a default scope of
DEFAULT, so that is the default scope value used when
searching for directory agents. If you want to search for
directory agents with scopes other than DEFAULT, complete
the following steps:
a. In the Scope field, type the name of a scope that you have
defined.
b. Click Add to add the scope to the list.
c. Repeat this procedure until you have added all the scopes.
Simple Network Management Protocol (SNMP) configuration
Configure SNMP IP addresses, optional SNMPv1 or SNMPv2c
community names, and SNMPv3.
When configuring SNMP IP addresses, you can add IP addresses
either individually or as a range, or you can import the addresses.
Adding a single IP address
a. Select Add a single IP address.
b. In the Single IP address or beginning range field, type the
IP address of the resource that you want to discover.
c. Click Add to add the IP address to the list.
d. Repeat this procedure until you have added all the IP
addresses.
Adding a range of IP addresses
a. Select Add a range of IP addresses.

44 IBMSystems Director Systems Management Guide

 b. For the IP address range that contains the resources that
you want to discover, type the low-end IP address value in
the Single IP address or beginning range field and the
high-end IP address value in the Ending range field.
c. Click Add to add the IP addresses to the list.
d. Repeat this procedure until you have added all the IP
addresses.
Importing IP addresses
a. Select Import.
b. In the Select the file that you want to import field, type in
the name of the import file or click Browse to search for
the file.

Note: Ensure that the file you use is a line delimited file
with one IP address on each line.
c. Click OK to import the IP addresses.
When configuring SNMPv1/v2c community names, select the protocol
that you want to use and add each community name to the list.
Specifying SNMPv1 or SNMPv2c community names for discovery
a. Select Use SNMPv1 to use the SNMPv1 protocol or
SNMPv2c to use the SNMPv2c protocol.
b. In the Community name field, type the name of a
community name that you have defined.
c. Click Add to add the community name to the list.
d. Repeat this procedure until you have added all the
community names.
When configuring SNMPv3 profiles, you can create new profiles or
edit or delete existing profiles.
Creating a SNMPv3 profile
a. Click Create a profile.
b. In the Profile name field, type a name for the profile.
c. In the User ID field, type a user ID to assign to the profile.
d. In the Authentication protocol field, select an
authentication protocol. Possible values are:
v None (If you select this option, skip to the Context
engine name (optional) field.)
v MD5
v SHA
e. In the Authentication password field, set a password for
authentication.
f. In the Confirm authentication password field, retype the
authentication password.
g. In the Privacy protocol field, select a privacy protocol.
Possible values are:
v None (If you select this option, skip to the Context
engine name (optional) field.)
v AES
v DES
h. In the Privacy password field, set a password for privacy.

Chapter 1. Overview 45
 i. In the Confirm privacy password field, retype the privacy
password.
j. In the Context engine name (optional) field, type the name
of any context engine that you want to specify.
k. In the Context engine ID (optional) field, type the ID of
the context engine.
l. Click Apply to add the profile to the SNMPv3 profiles list.
Deleting a SNMPv3 profile
a. In the SNMPv3 profiles list, select the profile that you
want to delete.
b. Click Delete a profile.
Editing a SNMPv3 profile
a. In the SNMPv3 profiles list, select the profile that you
want to edit.
b. Click Edit a profile.
c. Modify entries in the fields as needed.
d. Click Apply.
Storage Management Initiative Specification (SMI-S) configuration
Configure either a direct connection, multicast and broadcast, or a
proxy using directory agents. Also activate or deactivate access request
automation and activate or deactivate inventory discovery automation.

Note: You cannot configure directory agents for the following profile
types:
v Hardware management console
v Management controller
v Server, when discovering an IVM
Therefore, ensure that you configure multicast and broadcast if you
choose any of those profile types.
Select a discovery type at the top of the page to display options for
configuring that type.
When configuring a direct connection, you select a hardware type,
protocol, IP address, and port.
Configuring a direct connection
a. In the Hardware type field, select the type of hardware of
the resource to which you want to connect. Choose from
the following types:
v IBM System Storage DS3000/DS4000
v IBM System Storage DS6000
v QLogic fibre channel switch
v Brocade fibre channel switch
v IBM BladeCenter S SAS RAID Controller Module
b. In the Protocol field, select the protocol to use to make the
connection. Choose from the following protocols:
v https
v http

46 IBMSystems Director Systems Management Guide

 c. In the IP address field, specify the IPv4 IP address of the
resource.
d. In the Port field, specify the port on which the resource
listens.
When configuring multicast and broadcast, select to enable either and
set the timeout period.
Enabling multicast
Select Enable multicast to enable multicast.
Setting the timeout period
In the Timeout period (seconds) field, select the number of
seconds that the server will wait until timing out.
Enabling general broadcast
Select Enable general broadcast to enable general broadcast.
When configuring a proxy using directory agents, specify either an IP
address or a host name and set the scope.
Adding a directory agent using its IP address or host name
a. In the IP address or host name field, type the IP address
or host name of the directory agent that you want to
discover.
b. Click Add to add the IP address or host name to the list.
c. Repeat this procedure until you have added all the IP
addresses or host names.
Setting the scope
Each directory agent is associated with a scope. A discovery
request is targeted to find only those directory agents that are
associated with the specified scope. The directory agent
shipped with IBM Systems Director has a default scope of
DEFAULT, so that is the default scope value used when
searching for directory agents. If you want to search for
directory agents with scopes other than DEFAULT, complete
the following steps:
a. In the Scope field, type the name of a scope that you have
defined.
b. Click Add to add the scope to the list.
c. Repeat this procedure until you have added all the scopes.
When setting access request automation, you can choose to deactivate
or activate (with the appropriate login information) the feature.
Activating access request automation
a. Select Activate - use the following user login information.
b. In the User ID field, type a valid user ID for the resource.
c. In the Password field, type the password for the user ID.
Deactivating access request automation
a. Select Deactivate.
When setting inventory discovery automation, you can choose to
deactivate or activate (with an associated inventory profile) the
feature.
Activating inventory discovery automation
a. Select Activate - use the following inventory profile.
b. In the Inventory profiles list, select the profile that you
want to use for automatic inventory discovery.

Chapter 1. Overview 47
 Deactivating inventory discovery automation
a. Select Deactivate.
12. Click Next. The Summary page is displayed.
13. Click Finish.

When you are finished creating the profile, it will appear in the table on the
Advanced System Discovery page. You can then select the profile to run other
management tasks, such as copying it or editing it, or run the profile.
Related concepts
“Discovery” on page 231
“Manageable systems” on page 7
“Discovery protocols” on page 232
“System discovery” on page 237
“Discovery profiles” on page 239
Related tasks
“Managing access” on page 713
“Managing discovery profiles” on page 256
“Performing an advanced system discovery”
“Collecting and viewing inventory data” on page 259
“Discovering and collecting inventory for storage devices” on page 590

Performing an advanced system discovery

Use advanced system discovery to identify and manage a specific type of resource.
Advanced system discovery is helpful when you want to limit your discovery
using criteria that you specify.

Before performing an advanced system discovery, ensure that the discovery profile
that you want to use exists. If the profile that you want to use does not exist, you
must reconfigure an existing profile for your use or create a new one.

During advanced system discovery, IBM Systems Director Server attempts to

contact only the resource types that you specify by using the specific protocols
defined in the discovery profile. If IBM Systems Director Server successfully
contacts the resource, it is displayed in the appropriate groups in Navigate
Resources.

To perform an advanced system discovery, complete the following steps:

1. Open the Advanced System Discovery page using either of these two methods:
v On the Welcome page, click Advanced System Discovery under Optional
tasks.
v In the IBM Systems Director Web interface navigation area, expand
Inventory and then click Advanced System Discovery.
2. On the Advanced System Discovery page, select one or more discovery profiles
that you want to use for discovery.

Note: If the discovery profile that you want to use for the advanced system
discovery does not already exist, click Create to start the Advanced Discovery
Wizard.
3. Click Run. The Run - Advanced Systems Discovery page is displayed.
4. Use the Run - Advanced Systems Discovery page to set up optional functions
and options of your system discovery task:

48 IBMSystems Director Systems Management Guide

 Schedule
Use the Schedule page to set the discovery 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 page to choose options for an email notification
that you can receive as the discovery process progresses.
Options
Use the Options page to specify the time to use for the system time and
how to handle unavailable systems.
5. When you are finished with the Run - Advanced Systems Discovery page, click
OK. A discovery job is created and a message is displayed with buttons and
information 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 discovery is completed, the discovered systems are displayed in Navigate

Resources.

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.
Related concepts
“Discovery profiles” on page 239
“Discovery” on page 231
“Discovery protocols” on page 232
“System discovery” on page 237
“Inventory data and collection profiles” on page 259
Related tasks
“Creating a discovery profile” on page 34
“Managing discovery profiles” on page 256
“Accessing a secured system with request access” on page 714
“Discovering and collecting inventory for storage devices” on page 590
“Viewing active and scheduled job information” on page 205
“Finding and navigating resources” on page 95
“Managing inventory collection profiles” on page 262
“Collecting inventory” on page 68

How do I view my systems and groups?

In IBM Director Console version 5.20, you viewed groups in the Groups pane.
When you clicked a group, its members were displayed in the Group Contents
pane. In the IBM Systems Director Web interface, you no longer use panes. Instead,
you view your groups in Navigate Resources which displays groups in resource
views.

Chapter 1. Overview 49
 The default resource view is a table view. When you click on a group, you drill
down to the group members which can be more groups or individual systems and
their resources.

Navigate Resources is available in the navigation pane and from the Welcome
page. The All Systems group is equivalent to All Managed Objects group in IBM
Director 5.20.

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.

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 Navigate Resources, 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.

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 8. Table view

50 IBMSystems Director Systems Management Guide

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.

Chapter 1. Overview 51
 Related concepts
“Properties view”
“Topology Perspectives views” on page 53
Related tasks
“Navigating tables” on page 115
“Setting navigation preferences” on page 142

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 9. Properties view

52 IBMSystems Director Systems Management Guide

 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.

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” on page 50
“Topology Perspectives views”
Related tasks
“Working with properties” on page 139

Topology Perspectives views

After you select Navigate Resources 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,

Chapter 1. Overview 53
 such as BladeCenter chassis and blade servers, you can toggle among the map
view, resource view, or relationship view to manage your resources.

Navigate Resources 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
“Table view” on page 50
“Properties view” on page 52

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.

54 IBMSystems Director Systems Management Guide

Figure 10. Map 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
The toolbar contains the following toolbar buttons and menu:
Table 4. 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.

Chapter 1. Overview 55
Table 4. 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.

56 IBMSystems Director Systems Management Guide

 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.

Table state 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” on page 59
Related tasks
“Navigating topology maps” on page 128
“Reordering, minimizing, and hiding palettes” on page 135
“Viewing properties and details” on page 130
“Filtering the topology map” on page 132
“Working with topology maps” on page 127
“Viewing resources in the topology perspective” on page 62
“Changing between resource views” on page 66
“Changing the default resource view” on page 67
Related reference
“Topology-relationship descriptions” on page 137

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.

Chapter 1. Overview 57
Figure 11. Resource 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.

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.”
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

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.

58 IBMSystems Director Systems Management Guide

 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.

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
“Map view” on page 54
“Relationship view”
Related tasks
“Setting navigation preferences” on page 142
“Navigating tables” on page 115
Viewing resources in the resource view
“Changing between resource views” on page 66
“Changing the default resource view” on page 67

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.

Chapter 1. Overview 59
Figure 12. Relationship 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.

Actions
Contains actions for the selected resource and its related resources in a
relationship view.
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.”
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

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

60 IBMSystems Director Systems Management Guide

 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.

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.

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
“Map view” on page 54
“Resource view” on page 57
Related tasks
“Setting navigation preferences” on page 142
“Navigating tables” on page 115
Viewing resources in the relationship view
“Changing between resource views” on page 66
“Changing the default resource view” on page 67

Finding systems and other resources

A system-management environment can include a large number of systems and
other resources. While you can expand and navigate through groups in Navigate
Resources 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.

Note: Find a Resource is also available on the Welcome page.

Chapter 1. Overview 61
 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
IBM Systems Director Welcome page
“System severity states” on page 88
“Resource views” on page 96
“Properties view” on page 52
Related tasks
“Viewing the IBM Systems Director Server summary” on page 26
“Viewing resources in the topology perspective”
Working with tables
“Working with topology maps” on page 127
“Working with properties” on page 139
“Setting navigation preferences” on page 142
“Renaming a resource” on page 144
“Removing a resource” on page 145
“Using the Health Summary task to view the status of your environment” on page
288
“Using Navigate Resources to view the status of a specific resource” on page 296
Related reference
All possible ports
lssys command
accesssys command

Viewing resources in the topology perspective

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.

62 IBMSystems Director Systems Management Guide

Related concepts
“Resource views” on page 96
“Map view” on page 54
“Properties view” on page 52
Related tasks
“Finding systems and other resources” on page 61
Working with tables
“Working with topology maps” on page 127
“Working with properties” on page 139
“Setting navigation preferences” on page 142
“Renaming a resource” on page 144
“Removing a resource” on page 145
Related reference
“Topology-relationship descriptions” on page 137
lssys command
accesssys command

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
Chapter 1. Overview 63
 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” on page 54
“Resource view” on page 57
“Relationship view” on page 59
Related tasks
“Working with topology maps” on page 127
Viewing resources in the resource view
Viewing resources in the relationship view
“Changing between resource views” on page 66
“Changing the default resource view” on page 67
“Navigating topology maps” on page 128
“Viewing properties and details” on page 130
“Filtering the topology map” on page 132
“Determining a relationship type” on page 131
Related reference
“Topology-relationship descriptions” on page 137

Viewing resources in the resource view:

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.

64 IBMSystems Director Systems Management Guide

Related concepts
“Resource view” on page 57
“Map view” on page 54
“Relationship view” on page 59
Related tasks
Viewing resources in the map view
“Navigating tables” on page 115
Viewing resources in the relationship view
“Changing between resource views” on page 66
“Changing the default resource view” on page 67
Related reference
“Topology-relationship descriptions” on page 137

Viewing resources in the 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.

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.

Chapter 1. Overview 65
 Related concepts
“Relationship view” on page 59
“Map view” on page 54
“Resource view” on page 57
Related tasks
Viewing resources in the map view
Viewing resources in the resource view
“Navigating tables” on page 115
“Filtering table information” on page 118
“Changing between resource views”
“Changing the default resource view” on page 67
Related reference
“Topology-relationship descriptions” on page 137

Changing between resource views:

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.

66 IBMSystems Director Systems Management Guide

 Related concepts
“Map view” on page 54
“Resource view” on page 57
“Relationship view” on page 59
Related tasks
Viewing resources in the map view
Viewing resources in the resource view
Viewing resources in the relationship view
“Changing the default resource view”
Related reference
“Topology-relationship descriptions” on page 137

Changing the default resource view:

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.
3. 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. 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 concepts
“Map view” on page 54
“Resource view” on page 57
“Relationship view” on page 59
Related tasks
Viewing resources in the map view
Viewing resources in the resource view
Viewing resources in the relationship view
“Changing between resource views” on page 66
Related reference
“Topology-relationship descriptions” on page 137

How do I view my inventory?

In IBM Director Console version 5.20, you could view inventory by dragging the
task onto a managed system or group. In the IBM Systems Director Web interface,
the Inventory section of the navigation area provides a task to view and collect
inventory for a system or group.

Chapter 1. Overview 67
 You can choose from several predefined inventory profiles that filter only the
inventory items that you want to display.

Collecting inventory
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 or Advanced 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 → Request Access.

To collect inventory for one or more systems, complete the following steps:
1. Open the View and Collect Inventory page using either of these two methods:
v On the Welcome page, click Collect and view inventory under Optional
tasks.
v In the IBM Systems Director Web interface navigation area, expand
Inventory and then click View and Collect Inventory.
The View and Collect Inventory page is displayed.
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, complete 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 Manage inventory profiles 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 choose options for an email notification that
you can receive as the inventory collection process progresses.

68 IBMSystems Director Systems Management Guide

 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 a message is displayed with buttons and
information 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 View Inventory.
Related concepts
“Discovery” on page 231
“Manageable systems” on page 7
“Inventory data and collection profiles” on page 259
Related tasks
“Creating an inventory collection profile” on page 261
“Viewing inventory”
“Performing a system discovery” on page 32
“Performing an advanced system discovery” on page 48
“Viewing active and scheduled job information” on page 205

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 → Request Access.

To display inventory data for a resource, complete the following steps:

1. Open the View and Collect Inventory page using either of these two methods:
v On the Welcome page, click Collect and view inventory under Optional
tasks.
v In the IBM Systems Director Web interface navigation area, expand
Inventory and then click View and Collect Inventory.
The View and Collect Inventory page is displayed.
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, complete the following steps to add the system to the list.

Chapter 1. Overview 69
 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 Manage inventory profiles list, select the inventory profile that you
want to use.
4. Click View Inventory. The inventory data for the selected resource is
displayed.

Note: If you click View Inventory 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
“Inventory data and collection profiles” on page 259
Related tasks
“Collecting inventory” on page 68
“Creating an inventory collection profile” on page 261

Where are my tasks?

You can use this topic to map some common tasks in IBM Director 5.20 to their
location in the IBM Systems Director 6.1 interface.

The following table shows a list of tasks in IBM Director 5.20, and the
corresponding path to access those tasks in IBM Systems Director 6.1. For
step-by-step instructions for accessing a task in IBM Systems Director 6.1, click the
applicable link.

5.20 tasks and options How to access equivalent 6.1 tasks

Groups > All Managed Objects Navigate Resources > All systems
Discover systems On the Welcome page, click System
Discovery
Event Action Plans Automation > Automation Plans
Event Log Right-click a system and select System
Status and Health > Event Log
File Transfer Right-click a system and select System
Configuration > Remote Access > File
Transfer
Hardware Status System Status and Health > Health
Summary
Inventory Right-click a system and select Inventory >
View and Collect Inventory
Process Management Automation > Command Automation

70 IBMSystems Director Systems Management Guide

 5.20 tasks and options How to access equivalent 6.1 tasks
Remote Control Right-click a system and select System
Configuration > Remote Access > Remote
Control
Remote Session Right-click a system and select System
Configuration > Remote Access > Remote
Command Line
Resource Monitors Right-click a system and select Monitor
Resources
ServeRAID Manager System Configuration > External Storage
Applications
Scheduler Right-click a system and select a task. If the
task can be scheduled, the window is
displayed for creating a schedule
Software Distribution Release Management > Updates
Note: Most function from Software
Distribution (Standard Edition) is now
provided by Updates.

How do I start tasks?

In IBM Director Console version 5.20, you clicked tasks in the Tasks pane, dragged
tasks from the Tasks pane to a system or group, dragged systems or a group to a
task, or right-clicked a system. In the IBM Systems Director Web interface, you no
longer drag tasks, systems, or anything else. Instead, tasks are available in the
navigation area and the content area; when you right-click a resource a robust set
of applicable tasks is displayed.

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.

Chapter 1. Overview 71
 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
“Scheduling tasks.”

How do I create a hardware event automation plan?

You can create an event automation plan specifically for monitoring hardware
events from a system or group of systems.

To create a hardware event automation plan, complete the following steps:

1. On the Welcome page, click the Manage tab if the Manage page is not
displayed.
2. In the Automation Manager section, click Automation Plans.
3. On the Event Automation Plans page, click Create.
4. In the Event Automation Plan wizard, the Welcome page is displayed. Click
Next.
5. 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.
6. On the Targets page, select the systems that the event automation plan will
monitor for specific generated events. Select the systems in the Available list
and click Add > to move them to the Selected list. Click Next.
7. On the Events page, select Common from the Events list.
8. In the Event types list, select the categories of common events that you want
to monitor. You can select more than one category of events; however, you
must provide information for some of the categories. Provide this information
before you select another category of events. The following list describes the
hardware-related categories of common events that you can select as well as
the information each set requires.
Hardware
These categories of events are generated by the following hardware
and hardware components: processors (CPUs), disks, fans, memory,
network and switches, power supplies, security, servers, RAID or
storage arrays, and blade servers. None of these categories provide
additional settings.
Monitors
These events are generated by the monitors for microprocessor use,
memory use, and disk use. When you select one of these categories of
events, you must set the threshold values for the monitors. Then, a
threshold monitor is automatically created on the specified systems for
you. For more information, see “Managing monitors” and “Managing
thresholds.”

72 IBMSystems Director Systems Management Guide

Table 5. Categories of monitor events and available threshold settings
Categories of
events Available threshold settings
Processor use If you want the monitor to generate a critical event, select the Critical
check box. Then, select the percentage of processor use for the threshold.
When processor use is equal to or greater than the threshold setting, the
monitor will generate a Processor Use event with a critical severity.

If you want the monitor to generate a warning event, select the Warning
check box. Then, select the percentage of processor use for the threshold.
When processor use is equal to or greater than the threshold setting, the
monitor will generate a Processor Use event with a warning severity.
Note: You can set a threshold for both critical and warning events.
Memory use If you want the monitor to generate a critical event, select the Critical
check box. Then, select the amount of memory, in MB, to monitor for the
threshold. When the memory use is equal to or greater than the
threshold settings, the monitor will generate a Memory Use event with a
critical severity.

If you want the monitor to generate a warning event, select the Warning
check box. Then, select the amount of memory, in MB, to monitor for the
threshold. When the memory use is equal to or greater than the
threshold settings, the monitor will generate a Memory Use event with a
warning severity.
Note: You can set a threshold for both critical and warning events.
Disk use If you want the monitor to generate a critical event, select the Critical
check box. Then, select the percentage of disk capacity for the threshold.
When the used disk capacity is equal to or greater than the threshold
setting, the monitor will generate a Disk Use event with a critical
severity.

If you want the monitor to generate a warning event, select the Warning
check box. Then, select the percentage of disk capacity for the threshold.
When the used disk capacity is equal to or greater than the threshold
setting, the monitor will generate a Disk Use event with a warning
severity.
Note: You can set a threshold for both critical and warning events.

9. When you are satisfied with the specified event filters, click Next.
10. On the Events actions page, click Create.
11. In the Create Actions window, select an event action.
In most event automation plans, you will use one or more of the following
basic event actions:
v Send an alphanumeric page (using TAP)
v Send an e-mail (Internet SMTP)
v Send an e-mail to a mobile phone
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
For information about event action types, see “Event actions.”
12. Click OK.
13. 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.”

Chapter 1. Overview 73
 14. If you selected a basic event action, you can determine whether your settings
are correct by clicking Test.
15. If you selected a basic event action and you are satisfied with the settings,
click OK to save the event action.
16. When you are satisfied with your selected event actions, click Next. 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.
17. On the Time range page, click All day (24 x 7) to enable the plan to be active
all the time.
18. Click Next.
19. On the Summary page, verify the details of the event automation plan. If you
need to make changes, click < Back.
20. When you are done editing the event automation plan, click Finish.

74 IBMSystems Director Systems Management Guide

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 Welcome 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”)

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.”

Notes:

© Copyright IBM Corp. 1999, 2009 75

 1. For optimal performance, it is recommended that no more than 30 users log on
to IBM Systems Director Server at one time.
2. If you do not actively use the IBM Systems Director Web interface for 30
minutes, the automatic-timeout feature will log out your user ID from IBM
Systems Director Server.
Related concepts
“Users and user groups in IBM Systems Director” on page 688
“User authorization” on page 693
“Roles” on page 694
Related tasks
“Logging out of IBM Systems Director Server”
“Configuring Secure Sockets Layer between IBM Systems Director and the Web
browser client” on page 170
“Authorizing users to manage resources” on page 699

Logging out of IBM Systems Director Server

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.

Note: If you do not actively use the IBM Systems Director Web interface for 30
minutes, the automatic-timeout feature will log out your user ID from IBM
Systems Director Server.
Related tasks
“Logging into IBM Systems Director Server” on page 75

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 concepts
eLearning: Navigating in IBM Systems Director
eLearning: Scheduling tasks
Related tasks
“Navigating IBM Systems Director by way of the Welcome page” on page 80
“Finding and navigating resources” on page 95
“Finding and starting tasks” on page 161
“Scheduling tasks” on page 199
Related reference
lsgp command
accesssys command
Tasks and scheduled jobs commands

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

76 IBMSystems Director Systems Management Guide

 Systems Director and you can launch tasks in several other management tools. You
can access your resources using Navigate Resources.

Figure 13. 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 Navigate
Resources, Inventory, Health Summary, and Automation and Settings.

Content area
When you open the Web interface, by default you see the Welcome 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 77

 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.”
IBM Systems Director
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
“IBM Systems Director Welcome page” on page 17
Related tasks
“Setting navigation preferences” on page 142
“Customizing the Web interface”
“Managing and closing open pages in the Web interface” on page 79
“Viewing help in the Web interface” on page 80

Customizing 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:

78 IBMSystems Director Systems Management Guide

 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” on page 76
“IBM Systems Director Welcome page” on page 17
“Launched tasks and the IBM Systems Director Launched Tasks program” on page
161
Related tasks
“Managing and closing open pages in the Web interface”
“Viewing help in the Web interface” on page 80
“Setting navigation preferences” on page 142
“Starting tasks” on page 163
Related reference
runtask command

Managing and closing open pages in the Web interface

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

Chapter 2. Using the Web interface 79

 additional tabs.

Figure 14. 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” on page 76
“IBM Systems Director Welcome page” on page 17
Related tasks
“Customizing the Web interface” on page 78
“Viewing help in the Web interface”

Viewing help in the Web interface

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” on page 76
“IBM Systems Director Welcome page” on page 17
Related tasks
“Managing and closing open pages in the Web interface” on page 79
“Customizing the Web interface” on page 78

Navigating IBM Systems Director by way of the Welcome page

Using the IBM Systems Director Welcome 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 to expand your skills with IBM Systems Director.

80 IBMSystems Director Systems Management Guide

 Related concepts
eLearning: Navigating in IBM Systems Director
eLearning: Scheduling tasks
Related tasks
“Navigating the Web interface” on page 76
“Finding and navigating resources” on page 95
“Managing groups” on page 146
“Finding and starting tasks” on page 161
“Scheduling tasks” on page 199
Related reference
lsgp command
accesssys command
Tasks and scheduled jobs commands

IBM Systems Director Welcome page

Use the IBM Systems Director Welcome page to complete 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 to
expand your skills with IBM Systems Director.

Figure 15. The Welcome page displaying the Start, Manage, and Learn tabs

The following links are available at the top of the Welcome page:

Find a resource
Provides a way to quickly and easily find one or more resources in your
systems-management environment.

Find a task
Provides a way to quickly and easily find any task in IBM Systems
Director.

I’m a 5.20 user; how do I use 6.1?

Opens the IBM Systems Director information center to provide information
that describes how to use IBM Systems Director 6.1.0 compared to the
tasks in IBM Director version 5.20. This information is specifically designed
for IBM Director version 5.20 users that want to understand how to
complete familiar tasks using the new IBM Systems Director Web interface.

About
Displays the version of your IBM Systems Director installation.

Chapter 2. Using the Web interface 81

 Web resources
Displays other information resources that are available on the Web.

View updates
Checks for and displays any updates that are available from the IBM® Web
site that are required by IBM Systems Director Server.
Related concepts
“System severity states” on page 88
Related tasks
“Starting work in IBM Systems Director” on page 24
“Learning about the product” on page 28
“Checking IBM Systems Director readiness” on page 25
“Viewing updates” on page 28
“Viewing tutorials” on page 29
“Viewing the IBM Systems Director Server summary” on page 26

The Start page

Provides the tasks to perform initial discovery in your systems-management
environment, request access to your discovered resources, and collect inventory
from your resources. Then, use the next steps provided on this page to make IBM
Systems Director more productive. A user must have the AllPermission permission
to view this page; otherwise, it is not displayed. For more information, see
“Security.”

82 IBMSystems Director Systems Management Guide

Figure 16. The Welcome page interface displaying the Start page

Getting Started
Provides tasks and information that you can use to get started with IBM
Systems Director.

Chapter 2. Using the Web interface 83

 Discover
Performs initial discovery in your systems-management environment. This
discovery method searches the entire subnet of the server on which IBM
Systems Director Server is installed. It utilizes all the protocols that IBM
Systems Director uses to discover systems.

Status chart
Provides status information about resources that IBM Systems Director has
discovered. This information includes the number of operating systems
that are managed by way of the Common Agent, Platform Agent, or no
agent; the number of systems to which you do not have access, and the
number of systems on which inventory has not been collected. Click any of
these links to display detailed information about the affected systems and
resources.

Optional tasks
Provides optional tasks for getting started including the discovery,
inventory, and navigate resources.

Next Steps
Provides typical tasks for setting up IBM Systems Director, including
registering with IBM®, creating thresholds and event automation plans,
checking for updates, installing Common Agent on systems, setting up
security, and configuring your systems.
Related concepts
The Manage page
The Learn page
Related tasks
“Performing initial discovery” on page 235

The Manage page

Provides information that you can use to determine whether IBM Systems Director
and its plug-ins are ready to use. 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. After the initial discovery is completed, the
Manage page is displayed by default when you view the Welcome page.

The Manage tab includes an icon that is displayed if any problems exist with one
or more plug-ins.

Note: The Manage page displays only the plug-ins that the user is authorized to
use. If a user is not authorized to use any plug-ins, the Manage page is not
displayed.

Figure 17. The Manage tab with the Information icon

84 IBMSystems Director Systems Management Guide

The icon displayed is tied to the plug-in states that are displayed on the Manage
page:

If one or more plug-ins are in an Error state, the Error-connecting icon is

displayed on the Manage tab.

If one or more plug-ins are in the Setup-required state, the Setup-required

icon is displayed on the Manage tab.
No icon

If all plug-ins are in the ready state or collecting-data state ,

then no icon is displayed on the Manage tab.

Chapter 2. Using the Web interface 85

Figure 18. The Welcome page interface displaying the Manage page

86 IBMSystems Director Systems Management Guide

 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.
Related concepts
The Start page
The Learn page

The Learn page

Provides a list of available tutorial links. Each 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.

Chapter 2. Using the Web interface 87

Figure 19. The Welcome page interface displaying the Learn page

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 Start page
The Manage page

System severity states

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.

88 IBMSystems Director Systems Management Guide

 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
IBM Systems Director Welcome page
Related tasks
“Starting work in IBM Systems Director” on page 24
“Learning about the product” on page 28
“Checking IBM Systems Director readiness” on page 25
“Viewing updates” on page 28
“Viewing tutorials” on page 29
“Viewing the IBM Systems Director Server summary” on page 26

Starting work in IBM Systems Director

Before IBM Systems Director can manage your systems, the systems must be
discovered. Using the Welcome 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 Welcome page is
displayed automatically. Otherwise, in the IBM Systems Director navigation
area, click Welcome.
2. On the IBM Systems Director Welcome page, view the Getting Started section
on the Start page. This section provides status information about resources that
IBM Systems Director has discovered. This information includes the number of
operating systems that are managed by way of the Common Agent, Platform
Agent, or no agent; the number of systems to which you do not have access,
and the number of systems on which inventory has not been collected. Click
any of these links to display detailed information about the affected systems
and resources.

Note: If you have not performed discovery yet, discovery and system access
information is reported only for the management server.
In the Optional tasks area, the tasks that are commonly used when setting up
IBM Systems Director are provided.
3. View the Next Steps section on the Start page. This section provides typical
tasks for setting up IBM Systems Director, including registering with IBM®,
creating thresholds and event automation plans, checking for updates, installing
Common Agent on systems, setting up security, and configuring your systems.

Chapter 2. Using the Web interface 89

 Related concepts
IBM Systems Director Welcome page
“System severity states” on page 88
Learning and tutorials
Related tasks
“Learning about the product” on page 28
“Checking IBM Systems Director readiness” on page 25
“Viewing updates” on page 28
“Viewing tutorials” on page 29
“Viewing the IBM Systems Director Server summary” on page 26
Related reference
All possible ports

Learning about the product

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 Welcome. On the Welcome
page, click the Learn tab. View the available tutorials to expand your skills with
IBM Systems Director.
v On the Welcome page, click the Manage 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/systems/topic/director_6.1/fqm0_main.html 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
IBM Systems Director Welcome page
“System severity states” on page 88
Learning and tutorials
Related tasks
“Starting work in IBM Systems Director” on page 24
“Checking IBM Systems Director readiness” on page 25
“Viewing updates” on page 28
“Viewing tutorials” on page 29
“Viewing the IBM Systems Director Server summary” on page 26

Checking IBM Systems Director readiness

You can determine whether the plug-ins in your IBM Systems Director installation
are ready for use by viewing the Welcome page.

To determine whether plug-ins are ready for use, complete the following steps:
1. In the IBM Systems Director navigation area, click Welcome.
2. On the Welcome page, click the Manage tab.

90 IBMSystems Director Systems Management Guide

 3. Browse the Manage 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 Manage 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
IBM Systems Director Welcome page
“System severity states” on page 88
Learning and tutorials
Related tasks
“Starting work in IBM Systems Director” on page 24
“Learning about the product” on page 28
“Viewing updates” on page 28
“Viewing tutorials” on page 29
“Viewing the IBM Systems Director Server summary” on page 26
Related reference
All possible ports

Viewing updates
You can view updates that you can choose to apply to your IBM Systems Director
environment.

Chapter 2. Using the Web interface 91

 To view updates, in the IBM Systems Director navigation area, click Welcome to
view the Welcome page and complete any of the following steps:
v On the Welcome page, in the upper right-corner, click View updates. The View
Updates page is displayed.
v On the Start page, in the Next Steps section, click Check for updates on
discovered systems.
1. On the Check for Updates page, select the types of updates for which you
want check and click OK. Using the Check for Updates page, you can start
managing updates in the following ways:
– Select the systems to keep in compliance with the latest updates.
– Create an update group to contain the updates for your selected systems.
– Configure a connection to the Internet.
– Run or schedule a check for updates.
2. In the Run - Check for Updates window, click OK to start Check for Updates
immediately. IBM Systems Director checks for any updates that are available
from the IBM® Web site. A message is displayed stating that the Check for
Updates has run.
3. Click Show Updates. The Show Updates page is displayed.
v On the Welcome page, click the Manage tab. On the Manage page, view the
Update Manager section and click Check for Updates. The Check for Updates
page described in the preceding step is displayed.
Related concepts
IBM Systems Director Welcome page
“System severity states” on page 88
Learning and tutorials
Related tasks
“Starting work in IBM Systems Director” on page 24
“Learning about the product” on page 28
“Checking IBM Systems Director readiness” on page 25
“Viewing tutorials” on page 29
“Viewing the IBM Systems Director Server summary” on page 26
Related reference
All possible ports

Viewing tutorials
You can view tutorials to learn quickly how to use tasks and feature provided by
IBM Systems Director.

To view tutorials, complete the following steps:

1. In the IBM Systems Director navigation area, click Welcome.
2. On the Welcome page, click the Learn tab. The Learn page 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.”

92 IBMSystems Director Systems Management Guide

 Related concepts
IBM Systems Director Welcome page
“System severity states” on page 88
Learning and tutorials
Related tasks
“Starting work in IBM Systems Director” on page 24
“Learning about the product” on page 28
“Checking IBM Systems Director readiness” on page 25
“Viewing updates” on page 28
“Viewing the IBM Systems Director Server summary” on page 26
Related reference
All possible ports

Viewing the IBM Systems Director Server summary

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:
1. In the IBM Systems Director navigation area, click Welcome.
2. On the Welcome page, click the Manage tab.
3. On the Welcome page, 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.
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 Current management server statistics: 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 at a specific network
address or range of addresses.
Advanced system discovery
Click Advanced system discovery to discover a specific type of
resource or schedule a discovery task.

Chapter 2. Using the Web interface 93

 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.
Navigate resources
Click Navigate Resources 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.
v In the Common tasks area, the following links are provided:
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.”

94 IBMSystems Director Systems Management Guide

 Related concepts
IBM Systems Director Welcome page
“System severity states” on page 88
Learning and tutorials
Related tasks
“Starting work in IBM Systems Director” on page 24
“Learning about the product” on page 28
“Checking IBM Systems Director readiness” on page 25
“Viewing updates” on page 28
“Viewing tutorials” on page 29
“Finding systems and other resources” on page 61
“Finding a task” on page 162
Related reference
All possible ports

Finding and navigating resources

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.

Chapter 2. Using the Web interface 95

 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 concepts
eLearning: Navigating in IBM Systems Director
eLearning: Scheduling tasks
The Start page
“Discovery” on page 231
“Discovery protocols” on page 232
“System discovery” on page 237
Related tasks
“Navigating IBM Systems Director by way of the Welcome page” on page 80
“Navigating the Web interface” on page 76
“Managing groups” on page 146
“Finding and starting tasks” on page 161
“Scheduling tasks” on page 199
“Performing initial discovery” on page 235
“Performing an advanced system discovery” on page 48
Related reference
lsgp command
accesssys command
Tasks and scheduled jobs commands

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, Navigate
Resources 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 Navigate Resources, 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.

96 IBMSystems Director Systems Management Guide

 Related tasks
“Finding systems and other resources” on page 61
“Viewing resources in the topology perspective” on page 62
Working with tables
“Working with topology maps” on page 127
“Working with properties” on page 139
“Setting navigation preferences” on page 142
“Renaming a resource” on page 144
“Removing a resource” on page 145

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 20. 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

Chapter 2. Using the Web interface 97

 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” on page 52
“Topology Perspectives views” on page 53
Related tasks
“Navigating tables” on page 115
“Setting navigation preferences” on page 142

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

98 IBMSystems Director Systems Management Guide

 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 21. Properties 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.

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:

Chapter 2. Using the Web interface 99

 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” on page 50
“Topology Perspectives views” on page 53
Related tasks
“Working with properties” on page 139

Topology Perspectives views

After you select Navigate Resources 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,
such as BladeCenter chassis and blade servers, you can toggle among the map
view, resource view, or relationship view to manage your resources.

Navigate Resources 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”

100 IBMSystems Director Systems Management Guide

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
“Table view” on page 50
“Properties view” on page 52

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.

Chapter 2. Using the Web interface 101

Figure 22. Map 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
The toolbar contains the following toolbar buttons and menu:
Table 6. 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.

102 IBMSystems Director Systems Management Guide

Table 6. 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.

Chapter 2. Using the Web interface 103

 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.

Table state 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” on page 57
“Relationship view” on page 59
Related tasks
“Navigating topology maps” on page 128
“Reordering, minimizing, and hiding palettes” on page 135
“Viewing properties and details” on page 130
“Filtering the topology map” on page 132
“Working with topology maps” on page 127
“Viewing resources in the topology perspective” on page 62
“Changing between resource views” on page 66
“Changing the default resource view” on page 67
Related reference
“Topology-relationship descriptions” on page 137

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.

104 IBMSystems Director Systems Management Guide

Figure 23. Resource 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.

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.”
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

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.

Chapter 2. Using the Web interface 105

 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.

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
“Map view” on page 54
“Relationship view” on page 59
Related tasks
“Setting navigation preferences” on page 142
“Navigating tables” on page 115
Viewing resources in the resource view
“Changing between resource views” on page 66
“Changing the default resource view” on page 67

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.

106 IBMSystems Director Systems Management Guide

Figure 24. Relationship 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.

Actions
Contains actions for the selected resource and its related resources in a
relationship view.
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.”
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

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

Chapter 2. Using the Web interface 107

 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.

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.

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
“Map view” on page 54
“Resource view” on page 57
Related tasks
“Setting navigation preferences” on page 142
“Navigating tables” on page 115
Viewing resources in the relationship view
“Changing between resource views” on page 66
“Changing the default resource view” on page 67

Finding systems and other resources

A system-management environment can include a large number of systems and
other resources. While you can expand and navigate through groups in Navigate
Resources 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.

Note: Find a Resource is also available on the Welcome page.

108 IBMSystems Director Systems Management Guide

 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
IBM Systems Director Welcome page
“System severity states” on page 88
“Resource views” on page 96
“Properties view” on page 52
Related tasks
“Viewing the IBM Systems Director Server summary” on page 26
“Viewing resources in the topology perspective” on page 62
Working with tables
“Working with topology maps” on page 127
“Working with properties” on page 139
“Setting navigation preferences” on page 142
“Renaming a resource” on page 144
“Removing a resource” on page 145
“Using the Health Summary task to view the status of your environment” on page
288
“Using Navigate Resources to view the status of a specific resource” on page 296
Related reference
All possible ports
lssys command
accesssys command

Viewing resources in the topology perspective

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.

Chapter 2. Using the Web interface 109

 Related concepts
“Resource views” on page 96
“Map view” on page 54
“Properties view” on page 52
Related tasks
“Finding systems and other resources” on page 61
Working with tables
“Working with topology maps” on page 127
“Working with properties” on page 139
“Setting navigation preferences” on page 142
“Renaming a resource” on page 144
“Removing a resource” on page 145
Related reference
“Topology-relationship descriptions” on page 137
lssys command
accesssys command

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
110 IBMSystems Director Systems Management Guide
 Results page that displays the results of searching the map view. For more
information, see “Filtering the topology map.”
Related concepts
“Map view” on page 54
“Resource view” on page 57
“Relationship view” on page 59
Related tasks
“Working with topology maps” on page 127
Viewing resources in the resource view
Viewing resources in the relationship view
“Changing between resource views” on page 66
“Changing the default resource view” on page 67
“Navigating topology maps” on page 128
“Viewing properties and details” on page 130
“Filtering the topology map” on page 132
“Determining a relationship type” on page 131
Related reference
“Topology-relationship descriptions” on page 137

Viewing resources in the resource view

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.

Chapter 2. Using the Web interface 111

 Related concepts
“Resource view” on page 57
“Map view” on page 54
“Relationship view” on page 59
Related tasks
Viewing resources in the map view
“Navigating tables” on page 115
Viewing resources in the relationship view
“Changing between resource views” on page 66
“Changing the default resource view” on page 67
Related reference
“Topology-relationship descriptions” on page 137

Viewing resources in the 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.

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.

112 IBMSystems Director Systems Management Guide

Related concepts
“Relationship view” on page 59
“Map view” on page 54
“Resource view” on page 57
Related tasks
Viewing resources in the map view
Viewing resources in the resource view
“Navigating tables” on page 115
“Filtering table information” on page 118
“Changing between resource views” on page 66
“Changing the default resource view” on page 67
Related reference
“Topology-relationship descriptions” on page 137

Changing between resource views

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.

Chapter 2. Using the Web interface 113

 Related concepts
“Map view” on page 54
“Resource view” on page 57
“Relationship view” on page 59
Related tasks
Viewing resources in the map view
Viewing resources in the resource view
Viewing resources in the relationship view
“Changing the default resource view” on page 67
Related reference
“Topology-relationship descriptions” on page 137

Changing the default resource view

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.
3. 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. 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 concepts
“Map view” on page 54
“Resource view” on page 57
“Relationship view” on page 59
Related tasks
Viewing resources in the map view
Viewing resources in the resource view
Viewing resources in the relationship view
“Changing between resource views” on page 66
Related reference
“Topology-relationship descriptions” on page 137

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.

114 IBMSystems Director Systems Management Guide

Related concepts
“Resource views” on page 96
“Properties view” on page 52
Related tasks
“Finding systems and other resources” on page 61
“Viewing resources in the topology perspective” on page 62
“Working with properties” on page 139
“Working with topology maps” on page 127
“Setting navigation preferences” on page 142
“Renaming a resource” on page 144
“Removing a resource” on page 145
Related reference
lssys command
accesssys command

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 Navigate Resources, 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
Chapter 2. Using the Web interface 115
 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.

116 IBMSystems Director Systems Management Guide

Related concepts
“Table view” on page 50
“Properties view” on page 52
“Topology Perspectives views” on page 53
“Resource view” on page 57
“Relationship view” on page 59
“Groups” on page 146
Related tasks
Viewing resources in the resource view
Viewing resources in the relationship view
“Viewing properties”
“Filtering table information” on page 118
“Sorting table information” on page 120
“Searching table information” on page 121
“Printing tables” on page 121
“Exporting table information” on page 122
“Adding resources to your Favorites view” on page 123
“Adding a group of resources to the Health Summary” on page 124
“Setting table-navigation preferences” on page 125
“Setting table-column preferences” on page 126
“Adding a resource to an existing group” on page 158
Related reference
chgp command
chusergp command

Viewing properties
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.

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.

Chapter 2. Using the Web interface 117

 Related concepts
“Table view” on page 50
“Topology Perspectives views” on page 53
“Properties view” on page 52
Related tasks
“Navigating tables” on page 115
“Editing properties” on page 140
“Viewing properties and details” on page 130
“Filtering table information”
“Sorting table information” on page 120
“Searching table information” on page 121
“Printing tables” on page 121
“Exporting table information” on page 122
“Adding resources to your Favorites view” on page 123
“Adding a group of resources to the Health Summary” on page 124
“Setting table-navigation preferences” on page 125
“Setting table-column preferences” on page 126

Filtering table information

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.

118 IBMSystems Director Systems Management Guide

 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
The Filter window provides settings that are applicable to the specific
information reported in the column. For example, the following settings
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
The Filter window provides settings that are applicable to the specific
information reported in the column. For example, the following settings
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.

Chapter 2. Using the Web interface 119

 Related concepts
“Relationship view” on page 59
“Table view” on page 50
“Topology Perspectives views” on page 53
“Properties view” on page 52
Related tasks
Viewing resources in the relationship view
“Navigating tables” on page 115
“Viewing properties” on page 117
“Sorting table information”
“Searching table information” on page 121
“Printing tables” on page 121
“Exporting table information” on page 122
“Adding resources to your Favorites view” on page 123
“Adding a group of resources to the Health Summary” on page 124
“Setting table-navigation preferences” on page 125
“Setting table-column preferences” on page 126

Sorting table information

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.

120 IBMSystems Director Systems Management Guide

Related concepts
“Table view” on page 50
“Topology Perspectives views” on page 53
“Properties view” on page 52
Related tasks
“Navigating tables” on page 115
“Viewing properties” on page 117
“Filtering table information” on page 118
“Searching table information”
“Printing tables”
“Exporting table information” on page 122
“Adding resources to your Favorites view” on page 123
“Adding a group of resources to the Health Summary” on page 124
“Setting table-navigation preferences” on page 125
“Setting table-column preferences” on page 126

Searching table information

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 concepts
“Table view” on page 50
“Topology Perspectives views” on page 53
“Properties view” on page 52
Related tasks
“Navigating tables” on page 115
“Viewing properties” on page 117
“Filtering table information” on page 118
“Sorting table information” on page 120
“Printing tables”
“Exporting table information” on page 122
“Adding resources to your Favorites view” on page 123
“Adding a group of resources to the Health Summary” on page 124
“Setting table-navigation preferences” on page 125
“Setting table-column preferences” on page 126

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.

Chapter 2. Using the Web interface 121

 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 concepts
“Table view” on page 50
“Topology Perspectives views” on page 53
“Properties view” on page 52
Related tasks
“Navigating tables” on page 115
“Viewing properties” on page 117
“Filtering table information” on page 118
“Sorting table information” on page 120
“Searching table information” on page 121
“Exporting table information”
“Adding resources to your Favorites view” on page 123
“Adding a group of resources to the Health Summary” on page 124
“Setting table-navigation preferences” on page 125
“Setting table-column preferences” on page 126

Exporting table information

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.

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.

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.

122 IBMSystems Director Systems Management Guide

Related concepts
“Table view” on page 50
“Topology Perspectives views” on page 53
“Properties view” on page 52
Related tasks
“Navigating tables” on page 115
“Viewing properties” on page 117
“Filtering table information” on page 118
“Sorting table information” on page 120
“Searching table information” on page 121
“Printing tables” on page 121
“Adding resources to your Favorites view”
“Adding a group of resources to the Health Summary” on page 124
“Setting table-navigation preferences” on page 125
“Setting table-column preferences” on page 126

Adding resources to your Favorites view

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.

Chapter 2. Using the Web interface 123

 Related concepts
“Table view” on page 50
“Topology Perspectives views” on page 53
“Properties view” on page 52
Related tasks
“Navigating tables” on page 115
“Viewing properties” on page 117
“Filtering table information” on page 118
“Sorting table information” on page 120
“Searching table information” on page 121
“Printing tables” on page 121
“Exporting table information” on page 122
“Adding a group of resources to the Health Summary”
“Setting table-navigation preferences” on page 125
“Setting table-column preferences” on page 126

Adding a group of resources to the Health Summary

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.

124 IBMSystems Director Systems Management Guide

Related concepts
“Table view” on page 50
“Topology Perspectives views” on page 53
“Properties view” on page 52
Related tasks
“Navigating tables” on page 115
“Viewing properties” on page 117
“Filtering table information” on page 118
“Sorting table information” on page 120
“Searching table information” on page 121
“Printing tables” on page 121
“Exporting table information” on page 122
“Adding resources to your Favorites view” on page 123
“Managing groups” on page 146
“Setting table-navigation preferences”
“Setting table-column preferences” on page 126

Setting table-navigation preferences

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:

1. In the IBM Systems Director Web interface navigation area, expand Settings
and click Navigation Preferences.
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
Navigate Resources 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

Chapter 2. Using the Web interface 125

 table view for Health Summary and other navigation tables in IBM
Systems Director. The default number of rows is 10.
3. 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. 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 concepts
“Table view” on page 50
“Topology Perspectives views” on page 53
“Properties view” on page 52
Related tasks
“Navigating tables” on page 115
“Viewing properties” on page 117
“Filtering table information” on page 118
“Sorting table information” on page 120
“Searching table information” on page 121
“Printing tables” on page 121
“Exporting table information” on page 122
“Adding resources to your Favorites view” on page 123
“Adding a group of resources to the Health Summary” on page 124
“Setting table-column preferences”

Setting table-column preferences

You can customize your preferences for the table columns used in Navigate
Resources 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.

126 IBMSystems Director Systems Management Guide

 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.
6. 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. To reset the settings to the
system-defined values, click Restore Defaults. You still must click OK or
Apply to save the restored settings.

The table is adjusted to display using the new column settings.

Related concepts
“Table view” on page 50
“Topology Perspectives views” on page 53
“Properties view” on page 52
Related tasks
“Navigating tables” on page 115
“Viewing properties” on page 117
“Filtering table information” on page 118
“Sorting table information” on page 120
“Searching table information” on page 121
“Printing tables” on page 121
“Exporting table information” on page 122
“Adding resources to your Favorites view” on page 123
“Adding a group of resources to the Health Summary” on page 124
“Setting table-navigation preferences” on page 125

Working with topology maps

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.

Chapter 2. Using the Web interface 127

 Related concepts
“Resource views” on page 96
“Map view” on page 54
“Properties view” on page 52
Related tasks
“Finding systems and other resources” on page 61
“Viewing resources in the topology perspective” on page 62
Viewing resources in the map view
“Working with properties” on page 139
Working with tables
“Setting navigation preferences” on page 142
“Renaming a resource” on page 144
“Removing a resource” on page 145
Related reference
“Topology-relationship descriptions” on page 137
lssys command
accesssys command

Navigating topology maps

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.
Navigate Resources 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 7. 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.

128 IBMSystems Director Systems Management Guide

Table 7. Mouse actions in the topology map (continued)
Interaction Description
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.
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.

Chapter 2. Using the Web interface 129

 Related concepts
“Map view” on page 54
“Resource view” on page 57
“Relationship view” on page 59
“Properties view” on page 52
Related tasks
Viewing resources in the map view
“Viewing properties and details”
“Determining a relationship type” on page 131
“Filtering the topology map” on page 132
“Searching the topology map” on page 133
“Printing topology maps” on page 133
“Exporting topology maps” on page 134
“Reordering, minimizing, and hiding palettes” on page 135
“Setting topology-navigation preferences” on page 136
Related reference
“Topology-relationship descriptions” on page 137

Viewing properties and details

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.”

130 IBMSystems Director Systems Management Guide

Related concepts
“Map view” on page 54
“Resource view” on page 57
“Relationship view” on page 59
“Properties view” on page 52
Related tasks
Viewing resources in the map view
“Viewing properties” on page 117
“Navigating topology maps” on page 128
“Editing properties” on page 140
“Determining a relationship type”
“Filtering the topology map” on page 132
“Searching the topology map” on page 133
“Printing topology maps” on page 133
“Exporting topology maps” on page 134
“Reordering, minimizing, and hiding palettes” on page 135
“Setting topology-navigation preferences” on page 136
Related reference
“Topology-relationship descriptions” on page 137

Determining a relationship type

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.”

Chapter 2. Using the Web interface 131

 Related concepts
“Map view” on page 54
“Properties view” on page 52
Related tasks
Viewing resources in the map view
“Navigating topology maps” on page 128
“Viewing properties and details” on page 130
“Filtering the topology map”
“Searching the topology map” on page 133
“Printing topology maps” on page 133
“Exporting topology maps” on page 134
“Reordering, minimizing, and hiding palettes” on page 135
“Setting topology-navigation preferences” on page 136
Related reference
“Topology-relationship descriptions” on page 137

Filtering the topology map

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.

132 IBMSystems Director Systems Management Guide

Related concepts
“Map view” on page 54
“Resource view” on page 57
“Relationship view” on page 59
“Properties view” on page 52
Related tasks
Viewing resources in the map view
“Navigating topology maps” on page 128
“Viewing properties and details” on page 130
“Determining a relationship type” on page 131
“Searching the topology map”
“Printing topology maps”
“Exporting topology maps” on page 134
“Reordering, minimizing, and hiding palettes” on page 135
“Setting topology-navigation preferences” on page 136
Related reference
“Topology-relationship descriptions” on page 137

Searching the topology map

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 concepts
“Map view” on page 54
“Properties view” on page 52
Related tasks
“Navigating topology maps” on page 128
“Viewing properties and details” on page 130
“Determining a relationship type” on page 131
“Filtering the topology map” on page 132
“Printing topology maps”
“Exporting topology maps” on page 134
“Reordering, minimizing, and hiding palettes” on page 135
“Setting topology-navigation preferences” on page 136
Related reference
“Topology-relationship descriptions” on page 137

Printing topology maps

You can choose to print the entire topology or only a portion of the overall
topology.

Chapter 2. Using the Web interface 133

 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.

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 concepts
“Map view” on page 54
“Properties view” on page 52
Related tasks
“Navigating topology maps” on page 128
“Viewing properties and details” on page 130
“Determining a relationship type” on page 131
“Filtering the topology map” on page 132
“Searching the topology map” on page 133
“Exporting topology maps”
“Reordering, minimizing, and hiding palettes” on page 135
“Setting topology-navigation preferences” on page 136
Related reference
“Topology-relationship descriptions” on page 137

Exporting topology maps

You can export the topology-map data to a CSV file that you can subsequently
import into a spreadsheet 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.

To export data for an entire topology map, complete the following steps in a
topology map view:
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.

134 IBMSystems Director Systems Management Guide

Related concepts
“Map view” on page 54
“Properties view” on page 52
Related tasks
“Navigating topology maps” on page 128
“Viewing properties and details” on page 130
“Determining a relationship type” on page 131
“Filtering the topology map” on page 132
“Searching the topology map” on page 133
“Printing topology maps” on page 133
“Reordering, minimizing, and hiding palettes”
“Setting topology-navigation preferences” on page 136
Related reference
“Topology-relationship descriptions” on page 137

Reordering, minimizing, and hiding palettes

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.

Chapter 2. Using the Web interface 135

 Related concepts
“Map view” on page 54
“Resource view” on page 57
“Relationship view” on page 59
“Properties view” on page 52
Related tasks
“Navigating topology maps” on page 128
“Viewing properties and details” on page 130
“Determining a relationship type” on page 131
“Filtering the topology map” on page 132
“Searching the topology map” on page 133
“Printing topology maps” on page 133
“Exporting topology maps” on page 134
“Setting topology-navigation preferences”
Related reference
“Topology-relationship descriptions” on page 137

Setting topology-navigation preferences

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:

1. In the IBM Systems Director Web interface navigation area, expand Settings
and click Navigation Preferences.
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.
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.
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.

136 IBMSystems Director Systems Management Guide

 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.
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.
3. 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. 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 concepts
“Map view” on page 54
“Properties view” on page 52
Related tasks
“Navigating topology maps” on page 128
“Viewing properties and details” on page 130
“Determining a relationship type” on page 131
“Filtering the topology map” on page 132
“Searching the topology map” on page 133
“Printing topology maps” on page 133
“Exporting topology maps” on page 134
“Reordering, minimizing, and hiding palettes” on page 135
Related reference
“Topology-relationship descriptions”

Topology-relationship descriptions
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.

Chapter 2. Using the Web interface 137

 The following relationships are available:
Table 8. 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.
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.

138 IBMSystems Director Systems Management Guide

 Table 8. Types of relationship lines in the topology map (continued)
Type Description
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.
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
“Navigating topology maps” on page 128
“Viewing properties and details” on page 130
“Determining a relationship type” on page 131
“Filtering the topology map” on page 132
“Searching the topology map” on page 133
“Printing topology maps” on page 133
“Exporting topology maps” on page 134
“Reordering, minimizing, and hiding palettes” on page 135
“Setting topology-navigation preferences” on page 136

Working with properties

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.

Chapter 2. Using the Web interface 139

 Related concepts
“Resource views” on page 96
“Properties view” on page 52
“Table view” on page 50
“Topology Perspectives views” on page 53
Related tasks
“Finding systems and other resources” on page 61
“Viewing resources in the topology perspective” on page 62
Working with tables
“Working with topology maps” on page 127
“Setting navigation preferences” on page 142
“Renaming a resource” on page 144
“Removing a resource” on page 145
Related reference
lssys command
accesssys command

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 concepts
“Properties view” on page 52
Related tasks
“Viewing properties” on page 117
“Viewing properties and details” on page 130
“Viewing activities that affect a resource”
“Editing location information for a system” on page 141
“Editing location information for a group” on page 141
Related reference
“Topology-relationship descriptions” on page 137
chsys command

Viewing activities that affect a resource

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.

140 IBMSystems Director Systems Management Guide

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” on page 140
“Editing location information for a system”
“Editing location information for a group”
Related reference
chsys command

Editing location information for a system

You can edit the location information that you have provided for an individual
system. 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 system, 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” on page 140
“Viewing activities that affect a resource” on page 140
“Editing location information for a group”

Editing location information for a group

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 Navigate Resources, 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.

Chapter 2. Using the Web interface 141

 Related tasks
“Editing properties” on page 140
“Viewing activities that affect a resource” on page 140
“Editing location information for a system” on page 141

Setting navigation preferences

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:

1. In the IBM Systems Director Web interface navigation area, expand Settings
and click Navigation Preferences.
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.
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.
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

142 IBMSystems Director Systems Management Guide

 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
Navigate Resources 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.
3. 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. To reset the settings to the
system-defined values, click Restore Defaults. You still must click OK or
Apply to save the restored settings.

Chapter 2. Using the Web interface 143

 Related concepts
“The Web interface” on page 76
“IBM Systems Director Welcome page” on page 17
“Resource views” on page 96
“Table view” on page 50
“Properties view” on page 52
“Topology Perspectives views” on page 53
“Resource view” on page 57
“Map view” on page 54
“Relationship view” on page 59
Related tasks
“Customizing the Web interface” on page 78
“Finding systems and other resources” on page 61
“Viewing resources in the topology perspective” on page 62
“Working with properties” on page 139
Working with tables
“Working with topology maps” on page 127
“Renaming a resource”
“Removing a resource” on page 145
Related reference
lssys command
accesssys command

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.

144 IBMSystems Director Systems Management Guide

 Related concepts
“Resource views” on page 96
“Properties view” on page 52
Related tasks
“Finding systems and other resources” on page 61
“Viewing resources in the topology perspective” on page 62
“Working with properties” on page 139
Working with tables
“Working with topology maps” on page 127
“Setting navigation preferences” on page 142
“Removing a resource”
Related reference
lssys command
accesssys command
chsys command

Removing a resource
You can remove a resource from the IBM Systems Director database. The removal
does not affect the resource itself. 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.

Chapter 2. Using the Web interface 145

 Related concepts
“Resource views” on page 96
“Properties view” on page 52
Related tasks
“Finding systems and other resources” on page 61
“Viewing resources in the topology perspective” on page 62
“Working with properties” on page 139
Working with tables
“Working with topology maps” on page 127
“Setting navigation preferences” on page 142
“Renaming a resource” on page 144
Related reference
lssys command
accesssys command
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 Navigate
Resources, Health Summary, wizards, and throughout the IBM Systems Director
Web interface.
Related concepts
eLearning: Navigating in IBM Systems Director
eLearning: Scheduling tasks
Related tasks
“Navigating IBM Systems Director by way of the Welcome page” on page 80
“Finding and navigating resources” on page 95
“Adding a group of resources to the Health Summary” on page 124
“Finding and starting tasks” on page 161
“Scheduling tasks” on page 199
“Using the Health Summary task to view the status of your environment” on page
288
“Using Navigate Resources to view the status of a specific resource” on page 296
Related reference
lsgp command
accesssys command
Tasks and scheduled jobs commands

Groups
You can use IBM Systems Director to organize logical sets of resources into groups.

Groups have the following general characteristics:

146 IBMSystems Director Systems Management Guide

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 Navigate Resources, the resources that are members
of that group are displayed.
Related concepts
eLearning: Getting started tasks
Related tasks
“Creating a criteria-based dynamic group” on page 152
“Creating a static group” on page 155
“Editing a group” on page 156
“Deleting a group” on page 157
“Adding a resource to an existing group” on page 158
“Exporting a group” on page 159
“Importing a group” on page 160
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”
“Groups member types” on page 152

Default or predefined groups

When you start Navigate Resources, 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.

Chapter 2. Using the Web interface 147

 Note: You cannot edit or delete static default groups.
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 Server group that is
contained in the IBM Power Systems group.
– x86 Blade Servers
– Cell Blade 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
– MSVS Hosts
– Xen Hosts
– Scalable Systems
- Scalable Virtual Servers and Members
- Scalable Systems and Members
v System z
– HMC 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
– HMC and Managed Power Systems Servers
– IVM and Managed Power Systems Servers
– Virtual I/O Servers (VIOS) Appliances
– Power Servers

148 IBMSystems Director Systems Management Guide

 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 Servers (VIOS)
– 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.

Chapter 2. Using the Web interface 149

 Update Groups
All groups provided by update manager. For information, see “Update
groups.”
Virtualization Groups
All groups provided by virtualization manager. For information, see
“Virtualization groups.”
Related concepts
“Group types” on page 147
“Groups member types” on page 152

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:

Eligible Systems
Contains resources that Service and Support Manager can monitor, but are
not currently being monitored. You can see the Service and Support
Manager for information on starting monitoring for an eligible system.
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

150 IBMSystems Director Systems Management Guide

 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.

Virtualization groups:

IBM Systems Director organizes logical sets of resources into groups. Virtualization
manager provides a set of default or predefined groups for virtual resources.

The following table lists the names and descriptions of the groups provided by
virtualization manager.

Chapter 2. Using the Web interface 151

 Table 9. Virtualization manager groups
Group
Virtualization Groups
Platform Managers
Platform Managers and Members
Hosts
Virtual Servers
Virtual Servers and Hosts
Guest Operating Systems
Virtualization Systems
Virtual Farms
Description
Groups for managing virtualization
Systems capable of managing hosts or farms
Platform managers and their hosts or farms
Systems capable of hosting virtual servers
Virtual servers
Virtual servers and their hosts
Operating systems running on virtual
servers
Systems with virtualization capabilities,
attributes, or relationships
Virtual farms

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” on page 147
“Default or predefined groups” on page 147

Creating a criteria-based dynamic group

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

152 IBMSystems Director Systems Management Guide

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 Navigate Resources.
2. In Navigate Resources, 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 Navigate Resources, 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 154.

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.

Chapter 2. Using the Web interface 153

 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
153.
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 Navigate Resources. A

confirmation message about the group creation is displayed also.

154 IBMSystems Director Systems Management Guide

 Related concepts
“Groups” on page 146
eLearning: Getting started tasks
Related tasks
“Creating a static group”
“Editing a group” on page 156
“Deleting a group” on page 157
“Adding a resource to an existing group” on page 158
“Exporting a group” on page 159
“Importing a group” on page 160
Related reference
Group commands
mkgp command
chgp command
chusergp command
lsgp command

Creating a static group

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:

1. In the IBM Systems Director navigation area, click Navigate Resources.
2. In Navigate Resources, 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 Navigate Resources, a parent group is created and is located
under Personal Groups.

Chapter 2. Using the Web interface 155

 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 Navigate Resources. A confirmation

message about the group creation is displayed also.
Related concepts
“Groups” on page 146
eLearning: Getting started tasks
Related tasks
“Creating a criteria-based dynamic group” on page 152
“Editing a group”
“Deleting a group” on page 157
“Adding a resource to an existing group” on page 158
“Exporting a group” on page 159
“Importing a group” on page 160
Related reference
Group commands
mkgp command
chgp command
chusergp command
lsgp 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:

1. In the IBM Systems Director navigation area, click Navigate Resources.
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.

156 IBMSystems Director Systems Management Guide

 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 Navigate
Resources. A confirmation message about the group change is displayed also.
Related concepts
“Groups” on page 146
eLearning: Getting started tasks
Related tasks
“Creating a criteria-based dynamic group” on page 152
“Creating a static group” on page 155
“Deleting a group”
“Adding a resource to an existing group” on page 158
“Exporting a group” on page 159
“Importing a group” on page 160
Related reference
Group commands
mkgp command
chgp command
chusergp command
lsgp command

Deleting a group
When a group is no longer useful, you can delete it.

Note: You cannot edit or delete static default groups.

To delete a group, complete the following steps:

1. In the IBM Systems Director navigation area, click Navigate Resources.
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 Navigate Resources.

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.

Chapter 2. Using the Web interface 157

 Related concepts
“Groups” on page 146
eLearning: Getting started tasks
Related tasks
“Creating a criteria-based dynamic group” on page 152
“Creating a static group” on page 155
“Editing a group” on page 156
“Adding a resource to an existing group”
“Exporting a group” on page 159
“Importing a group” on page 160
Related reference
Group commands
mkgp command
chgp command
chusergp command
lsgp command

Adding a resource to an existing group

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:
1. In the IBM Systems Director navigation area, click Navigate Resources.
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.

158 IBMSystems Director Systems Management Guide

 Related concepts
“Groups” on page 146
eLearning: Getting started tasks
Related tasks
“Creating a criteria-based dynamic group” on page 152
“Creating a static group” on page 155
“Editing a group” on page 156
“Deleting a group” on page 157
“Navigating tables” on page 115
“Exporting a group”
“Importing a group” on page 160
Related reference
Group commands
mkgp command
chgp command
chusergp command
lsgp 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.

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.

To export a group, complete the following steps:

1. In the IBM Systems Director navigation area, click Navigate Resources.
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. 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.

Chapter 2. Using the Web interface 159

 Related concepts
“Groups” on page 146
eLearning: Getting started tasks
Related tasks
“Creating a criteria-based dynamic group” on page 152
“Creating a static group” on page 155
“Editing a group” on page 156
“Deleting a group” on page 157
“Adding a resource to an existing group” on page 158
“Importing a group”
Related reference
Group commands
mkgp command
chgp command
chusergp command
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:

1. In the IBM Systems Director navigation area, click Navigate Resources.
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 Navigate Resources. 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.

160 IBMSystems Director Systems Management Guide

 Related concepts
“Groups” on page 146
eLearning: Getting started tasks
Related tasks
“Creating a criteria-based dynamic group” on page 152
“Creating a static group” on page 155
“Editing a group” on page 156
“Deleting a group” on page 157
“Adding a resource to an existing group” on page 158
“Exporting a group” on page 159
Related reference
Group commands
mkgp command
chgp command
chusergp command
lsgp command

Finding and starting tasks

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 concepts
eLearning: Navigating in IBM Systems Director
eLearning: Scheduling tasks
Related tasks
“Navigating IBM Systems Director by way of the Welcome page” on page 80
“Finding and navigating resources” on page 95
“Navigating the Web interface” on page 76
“Managing groups” on page 146
“Scheduling tasks” on page 199
Related reference
lsgp command
accesssys command
Tasks and scheduled jobs commands

Launched tasks and the IBM Systems Director Launched

Tasks program
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:

Chapter 2. Using the Web interface 161

 v In another instance of your Web browser. The task provides its own Web
interface.
v As a separate program on your system desktop.
v The IBM Systems Director Launched Tasks program is displayed and opens the
task that you selected.

IBM Systems Director provides some tasks that still require a client-based
application. This application is called the IBM Systems Director Launched Tasks
program. The IBM Systems Director Launched Tasks program can open the
following tasks:
v Event Action Editor (used to create advanced event actions)
v Event Filter Builder (used to create advanced event filters)
v File Transfer
v Command Automation (formerly called Process Management - Tasks)
v Remote Session
v SNMP Browser
v MIB Management

Note: The IBM Systems Director Launched Tasks program is installed

automatically the first time you use a task that requires it. Because the IBM
Systems Director Launched Tasks program opens outside of the IBM Systems
Director Web interface, Java Web Start (JWS) is also provided for installation. For
more information, see “Downloading Java Web Start.”
Related tasks
“Downloading Java Web Start” on page 166
“Finding a task”
“Starting tasks” on page 163
“Starting the IBM Systems Director Launched Tasks program” on page 164
Related reference
Troubleshooting for launched 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.

Note: Find a Task is also available on the Welcome page.

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

162 IBMSystems Director Systems Management Guide

 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
IBM Systems Director Welcome page
“System severity states” on page 88
“Launched tasks and the IBM Systems Director Launched Tasks program” on page
161
Related tasks
“Viewing the IBM Systems Director Server summary” on page 26
“Starting tasks”
“Starting the IBM Systems Director Launched Tasks program” on page 164
Integrating external applications into IBM Systems Director
“Viewing the discovery manager summary” on page 233
Related reference
All possible ports
Troubleshooting for launched tasks
lstask command
runtask 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.

Chapter 2. Using the Web interface 163

 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
“Scheduling tasks.”

Some tasks in IBM Systems Director require a client-based application: the IBM
Systems Director Launched Tasks program. This program is installed automatically
the first time you use a task that requires it. Because the IBM Systems Director
Launched Tasks program opens outside of the IBM Systems Director Web interface,
Java Web Start (JWS) is required. If your Web browser does not have JWS installed
already, a prompt is displayed to download and install JWS. If your Web browser
has a version of JWS installed that is not compatible with the IBM Systems Director
Launched Tasks program, a compatible version of JWS is installed automatically.
For more information, see “Starting the IBM Systems Director Launched Tasks
program.”
Related concepts
“Launched tasks and the IBM Systems Director Launched Tasks program” on page
161
Related tasks
“Finding a task” on page 162
“Scheduling tasks” on page 199
“Customizing the Web interface” on page 78
“Starting the IBM Systems Director Launched Tasks program”
Integrating external applications into IBM Systems Director
Related reference
Troubleshooting for launched tasks
lstask command
runtask command

Starting the IBM Systems Director Launched Tasks program

Some tasks in IBM Systems Director require a client-based application: the IBM
Systems Director Launched Tasks program. This program is installed automatically
the first time you use a task that requires it. Because the IBM Systems Director
Launched Tasks program opens outside of the IBM Systems Director Web interface,
Java Web Start (JWS) is required. If your Web browser does not have JWS installed
already, a prompt is displayed to download and install JWS. If your Web browser
has a version of JWS installed that is not compatible with the IBM Systems Director
Launched Tasks program, a compatible version of JWS is installed automatically.

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.

164 IBMSystems Director Systems Management Guide

However, if the Java Web Start installation does not succeed as expected, complete
the following steps to enable the IBM Systems Director Launched Tasks program
and start launched tasks using the IBM Systems Director Launched Tasks program:
1. Download the Java Web Start software to your browser system. For more
information, see “Downloading Java Web Start.”
2. Make sure that your browser system is configured to use Java Web Start. For
more information, see “Configuring Web browsers to use Java Web Start.”
3. Start a launched task. If you are starting a launched task for the first time on
your browser system, an automatic installation of the IBM Systems Director
Launched Tasks program starts.

Note: When starting tasks from the IBM Systems Director Web interface using
Mozilla Firefox, the Opening launch.jnlp window might open and display a
message asking what to do with the .jnlp file. To make sure that the launched
task can proceed and that this message is not displayed in the future, it is
recommended that you select Open with Java Web Start Launcher and Do this
automatically for files like this from now on.

Chapter 2. Using the Web interface 165

 Related concepts
“Launched tasks and the IBM Systems Director Launched Tasks program” on page
161
External-application tasks
Related tasks
“Finding a task” on page 162
“Starting tasks” on page 163
Integrating external applications into IBM Systems Director
Configuring external-application tasks for browser systems
“Managing SNMP devices” on page 323
“Compiling a MIB file” on page 324
“Selecting MIB files to load into memory” on page 324
“Viewing SNMP device attributes” on page 323
“Managing process monitors” on page 325
“Applying a process monitor” on page 326
“Creating a process monitor” on page 325
“Removing all process monitors” on page 327
“Viewing process monitors” on page 325
“Exporting resource-monitor statistics” on page 328
“Recording resource-monitor statistics” on page 327
“Removing a resource-monitor record” on page 329
“Viewing a graph of a resource-monitor recording” on page 328
“Creating a command definition” on page 329
Related reference
Troubleshooting for launched tasks
lstask command
runtask command
Launched tasks troubleshooting
“Monitoring system resources” on page 327

Downloading Java Web Start

If you want to use the IBM Systems Director Launched Tasks program, 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.

166 IBMSystems Director Systems Management Guide

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 concepts
“Launched tasks and the IBM Systems Director Launched Tasks program” on page
161
External-application tasks
Related tasks
“Configuring Web Browsers to use Java Web Start”
“Configuring Secure Sockets Layer between IBM Systems Director and the Web
browser client” on page 170
Configuring external-application tasks for browser systems
Related reference
Troubleshooting for launched tasks

Configuring Web Browsers to use Java Web Start

In order to launch tasks, including those that use the IBM Systems Director
Launched Tasks program, Web browsers must use the IBM® Java Web Start
program that is installed with the IBM® Java Runtime Environment (JRE).
Related tasks
“Downloading Java Web Start” on page 166
“Configuring Secure Sockets Layer between IBM Systems Director and the Web
browser client” on page 170

Updating the Firefox Web browser to use the IBM® Java Web Start program:

In order to launch tasks, including those that use the IBM Systems Director
Launched Tasks program, the Firefox Web browser must use the IBM® Java Web
Start program that is installed with the IBM® Java Runtime Environment (JRE).

To update the Firefox Web browser, version 2.0.0.6, to use the IBM® Java Web Start
program, complete the following steps:
1. In the Web browser, click Tools → Options.
2. In the Options window, click Content from the toolbar.
3. On the Content page, click Manage.
4. In the Download Actions window, select the JNLP file type and click Change
Action.

Note: If the JNLP file type is not available, see “Associating the JNLP file type
with the Java Web Start program (Firefox).”
5. In the Change Action window, select Open them with this application and
click Browse.
6. Navigate to the Java Web Start program, javaws.exe, located in the IBM® JRE
directory.
7. In the bin directory, select the javaws.exe program and click Open.
8. In the Change Action window, click OK.
9. In the Download Actions window, click Close.

Chapter 2. Using the Web interface 167

 10. In the Options window, click OK. The Java Web Start program and the IBM®
JRE are now configured for use with the IBM Systems Director Launched
Tasks program and other launched tasks.
Related tasks
“Associating the JNLP file type with the Java Web Start program (Firefox)”

Associating the JNLP file type with the Java Web Start program (Firefox):

If, while updating the Firefox Web browser to use the IBM® 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
IBM® 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 Open with list, select Other.
3. Navigate to the Java Web Start program, javaws.exe, located in the IBM® JRE
directory.
4. In the bin directory, select the javaws.exe program and click Open.
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 the Firefox Web browser to use the IBM® Java Web Start program” on
page 167

Updating the Microsoft Internet Explorer Web browser to use the IBM® Java
Web Start program:

In order to launch tasks, including those that use the IBM Systems Director
Launched Tasks program, the Microsoft Internet Explorer Web browser must use
the IBM® Java Web Start program that is installed with the IBM® Java Runtime
Environment (JRE).

To update the Microsoft Internet Explorer Web browser, versions 6.0 or 7.0, to use
the IBM® 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,
complete the following steps:
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.

168 IBMSystems Director Systems Management Guide

 7. In the Editing action for type window, click Browse.
8. Navigate to the Java Web Start program, javaws.exe, located in the IBM® JRE
directory.
9. In the bin directory, select the javaws.exe program and click Open.
10. In the Editing action for type window, type 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 IBM® JRE are now configured for use with the IBM Systems Director
Launched Tasks program and other launched tasks.
Related tasks
“Associating the JNLP file type with the Java Web Start program (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 IBM®
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 IBM® 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.
13. Navigate to the Java Web Start program, javaws.exe, located in the IBM® JRE
directory.
14. In the bin directory, select the javaws.exe program and click Open.
15. Click OK.
16. In the Edit File Type window, click OK.
17. In the Folder Options window, click Close. The Java Web Start program and
the IBM® JRE are now configured for use with the IBM Systems Director
Launched Tasks program and other launched tasks.

Chapter 2. Using the Web interface 169

 Related tasks
“Updating the Microsoft Internet Explorer Web browser to use the IBM® Java Web
Start program” on page 168

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. However, to ensure server authentication, data
privacy, and data integrity, you must replace the default certificate with either a
self-signed certificate or a certificate that is signed by a certificate authority (CA)
and you must 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: 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.

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 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.”
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.”
Related tasks
“Logging into IBM Systems Director Server” on page 75
“Downloading Java Web Start” on page 166
“Configuring Web Browsers to use Java Web Start” on page 167

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.

170 IBMSystems Director Systems Management Guide

Note: Back up any files before you edit them.

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/lwi/security/keystore/
ibmjsse2.jks
For Windows install_root\lwi\security\keystore\
ibmjsse2.jks

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 (/).
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.

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.”

Chapter 2. Using the Web interface 171

 Related tasks
“Creating a self-signed certificate”
“Requesting a CA signed certificate” on page 173

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.

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
container properties.”

172 IBMSystems Director Systems Management Guide

Related tasks
“Deleting the default certificate” on page 170
“Requesting a CA signed certificate”
“Updating the Web container properties” on page 176

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.”

Chapter 2. Using the Web interface 173

 Related tasks
“Deleting the default certificate” on page 170
“Creating a self-signed certificate” on page 172
“Receiving a CA signed certificate”
“Updating the Web container properties” on page 176

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. Messages and settings might differ depending on your Web browser and the
version of Java Web Start that you are running.
3. 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.
If you are importing a certificate with a file extension of .pfx and errors
indicate that the certificate store is corrupt, see Resolving the iKeyman Corrupted
Database Message. Go to the IBM® Support and Download Web site at
www.ibm.com/support/us and search using the reference number PRS2855.

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/lwi/security/keystore
For Windows install_root\lwi\security\keystore

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 (/).

174 IBMSystems Director Systems Management Guide

 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

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 (/).
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/lwi/security/keystore/
ibmjsse2.jks
For Windows install_root\lwi\security\keystore\
ibmjsse2.jks

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 (/).
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/lwi/security/keystore
For Windows install_root\lwi\security\keystore

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 (/).
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.

Chapter 2. Using the Web interface 175

 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
container properties.”
Related tasks
“Requesting a CA signed certificate” on page 173
“Updating the Web container properties”

Updating the Web container properties:

Because you changed the keystore password, you must update the Web container
properties with the new keystore 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:
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.

To update the Web container properties, complete the following steps:

1. 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

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 (/).

176 IBMSystems Director Systems Management Guide

 2. Change the name of the webcontainer.properties file to
webcontainer.properties.bak.
3. In the same directory, create a file named sslconfig and copy the contents of
webcontainer.properties.bak to the sslconfig file.
4. Using a text editor, edit the sslconfig file.

Notes:
a. Specify only plain text values for the passwords in the sslconfig file.
b.
5. Specify com.ibm.ssl.keyStorePassword.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 172 in “Creating a self-signed certificate”
– Step 19 on page 176 in “Receiving a CA-signed certificate”
6. Specify the default password ibmpassw0rd for the truststore file, in plain text:
com.ibm.ssl.trustStorePassword.secure_port=ibmpassw0rd

where secure_port is the secure port that IBM Systems Director Server uses.
Use the secure port value indicated in your properties file.
7. Delete the line sslEnabled=true from the sslconfig file.
8. Save the sslconfig file.
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.

Next, you must update the Web browser with the new certificate. Go to “Updating
the Web browser with the new certificate.”

Chapter 2. Using the Web interface 177

 Related tasks
“Creating a self-signed certificate” on page 172
“Receiving a CA signed certificate” on page 174
“Requesting a CA signed certificate” on page 173
“Updating the Web browser with the new certificate”

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 certificate, complete the following steps.

Note: If you performed step 17 on page 175 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. 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.

178 IBMSystems Director Systems Management Guide

 Related tasks
“Updating the Web container properties” on page 176

Integrating external applications into IBM Systems Director

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
IBM Systems Director.

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 concepts
“Launched tasks and the IBM Systems Director Launched Tasks program” on page
161
Related tasks
“Starting tasks” on page 163
“Authorizing users to IBM Systems Director” on page 693
“Finding a task” on page 162
“Starting the IBM Systems Director Launched Tasks program” on page 164
Related reference
runtask command

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
Chapter 2. Using the Web interface 179
 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” on page 181
“Considerations for command-string parameters” on page 188
“Environment variables for external-application tasks” on page 189
“Managed-resource types for the Client.x.Resource parameter” on page 191
“Sample command-task files” on page 192

Command-task file location and naming conventions:

All command-task files must meet specific file-location and naming-convention

requirements.

180 IBMSystems Director Systems Management Guide

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”
“Considerations for command-string parameters” on page 188
“Environment variables for external-application tasks” on page 189
“Managed-resource types for the Client.x.Resource parameter” on page 191
“Sample command-task files” on page 192

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.”

Chapter 2. Using the Web interface 181

Table 10. 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

182 IBMSystems Director Systems Management Guide

Table 10. Command-task parameters (continued)
Parameter name
CommandString
CommandString.Linux
CommandString.Unix
CommandString.VMware
CommandString.Windows
CommandString.Windows2003
CommandString.WindowsXP
CommandString.WindowsVista
CommandString.Server
CommandString.Server.Linux
CommandString.Server.Unix
CommandString.Server.VMware
CommandString.Server.Windows
CommandString.Server.Windows2003
CommandString.Server.WindowsXP
CommandString.Server.WindowsVista
Description Allowed values
The command string to be run on a A valid command line for
UNIX®, Linux, VMware, or Windows an external application
(including Windows 2003, Windows XP, running on a browser
and Windows Vista) browser system. system.
Note:
v You can specify both
CommandString.Server and
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.
The command string to be run on a UNIX, A valid command line for
Linux, VMware, or Windows (including an external application on a
Windows 2003, Windows XP, and Windows management server.
Vista) management server.
Note:
v You can specify both
CommandString.Server and
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.
Chapter 2. Using the Web interface 183
Table 10. Command-task parameters (continued)
Parameter name Description Allowed values
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
Systems Director uses the
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.

184 IBMSystems Director Systems Management Guide

Table 10. Command-task parameters (continued)
Parameter name Description Allowed values
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.

Chapter 2. Using the Web interface 185

Table 10. Command-task parameters (continued)
Parameter name Description Allowed values
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.

186 IBMSystems Director Systems Management Guide

Table 10. Command-task parameters (continued)
Parameter name Description Allowed values
Targeted A flag that specifies whether the Specify one of the following
external-application task can be started as a values:
targeted task, an untargeted task, or both.
none An untargeted
If this parameter is omitted, the value is set
task. The task can
to one.
be opened by
selecting it in the
IBM Systems
Director Web
interface
navigation 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 Web
interface
navigation pane,
from the Actions
menu, from the
pop-up menu, or
can be started by
selecting a target
system and
right-clicking the
task. This is the
default value.
multi A targeted task.
The task can be
started by selecting
a target system and
right-clicking the
task. This is the
default value.
none|multi
Tasks that are both
targeted and
untargeted. The
task can be opened
by selecting it in
the IBM Systems
Director Web
interface
navigation pane,
from the Actions
Chapter 2. Using the Web interface
menu, from the
187
pop-up menu, or
can be started by
 Related concepts
Targeted and untargeted tasks
Related tasks
“Specifying national-language task titles” on page 193
Related reference
“Command-task file location and naming conventions” on page 180
“Considerations for command-string parameters”
“Environment variables for external-application tasks” on page 189
“Managed-resource types for the Client.x.Resource parameter” on page 191
“Sample command-task files” on page 192

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

188 IBMSystems Director Systems Management Guide

 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
Targeted and untargeted tasks
Related reference
“Command-task file location and naming conventions” on page 180
“Command-task file parameters” on page 181
“Environment variables for external-application tasks”
“Managed-resource types for the Client.x.Resource parameter” on page 191
“Sample command-task files” on page 192

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.

Chapter 2. Using the Web interface 189

 You can access the value associated with a system property using the echo
command. The following table provides an example.
Table 11. 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 12. 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

190 IBMSystems Director Systems Management Guide

Table 12. System properties (continued)
System property Environment variable name
Task CMDTASK_TASKv_x
URL CMDTASK_URL_x
WBEMPort CMDTASK_WBEMPORT_x

Related concepts
Targeted and untargeted tasks
Related reference
“Command-task file location and naming conventions” on page 180
“Command-task file parameters” on page 181
“Considerations for command-string parameters” on page 188
“Managed-resource types for the Client.x.Resource parameter”
“Sample command-task files” on page 192

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 13.

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 13. 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

Chapter 2. Using the Web interface 191

 Related concepts
Targeted and untargeted tasks
Related reference
“Command-task file location and naming conventions” on page 180
“Command-task file parameters” on page 181
“Considerations for command-string parameters” on page 188
“Environment variables for external-application tasks” on page 189
“Sample command-task files”

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.
# Parameters for all operating systems:
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.
# Parameters for all operating systems:
#On Windows:
CommandString.Server.Windows = myServerApp.exe %CMDTASK_MO_MFG_0%
%CMDTASK_MO_MACHINETYPEMODEL_0%

192 IBMSystems Director Systems Management Guide

Related concepts
Targeted and untargeted tasks
Related reference
“Command-task file location and naming conventions” on page 180
“Command-task file parameters” on page 181
“Considerations for command-string parameters” on page 188
“Environment variables for external-application tasks” on page 189
“Managed-resource types for the Client.x.Resource parameter” on page 191

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
External-application tasks
Related tasks
“Refreshing external-application tasks in the IBM Systems Director Web interface”
on page 196
Starting external-application tasks in the IBM Systems Director Web interface
“Deleting an external-application task” on page 198
“Specifying national-language task titles”
Configuring external-application tasks for browser systems
Related reference
“Command-task file location and naming conventions” on page 180
“Command-task file parameters” on page 181
“Considerations for command-string parameters” on page 188

Specifying national-language task titles

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

Chapter 2. Using the Web interface 193

 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 14. 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.

194 IBMSystems Director Systems Management Guide

3. Copy the resource-bundle files to the applicable directory on the management
server.
Table 15. Location of resource-bundle files by operating system
Windows \Program Files\IBM\Director\classes\CmdTask\resources
installation
Linux /opt/IBM/director/classes/CmdTask/resources
installation

where resources represents the directory that contains resource files for a specific
external-application task.
Related concepts
Targeted and untargeted tasks
External-application tasks
Related tasks
“Refreshing external-application tasks in the IBM Systems Director Web interface”
on page 196
Starting external-application tasks in the IBM Systems Director Web interface
“Deleting an external-application task” on page 198
“Creating a command-task file” on page 193
Configuring external-application tasks for browser systems
Related reference
“Command-task file parameters” on page 181
“Command-task file location and naming conventions” on page 180
“Considerations for command-string parameters” on page 188
“Environment variables for external-application tasks” on page 189
“Managed-resource types for the Client.x.Resource parameter” on page 191
“Sample command-task files” on page 192

Configuring external-application tasks for browser systems

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.

Chapter 2. Using the Web interface 195

 Note: This task requires the IBM Systems Director Launched Tasks program.
This program is installed automatically the first time you use a task that requires
it. For information about the IBM Systems Director Launched Tasks program, see
“Starting the IBM Systems Director Launched Tasks program.”
Related concepts
External-application tasks
Related tasks
“Refreshing external-application tasks in the IBM Systems Director Web interface”
Starting external-application tasks in the IBM Systems Director Web interface
“Deleting an external-application task” on page 198
“Creating a command-task file” on page 193
“Starting the IBM Systems Director Launched Tasks program” on page 164
“Downloading Java Web Start” on page 166
“Specifying national-language task titles” on page 193
Related reference
“Command-task file location and naming conventions” on page 180
“Command-task file parameters” on page 181
“Considerations for command-string parameters” on page 188

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. In the IBM Systems Director Web interface navigation area, expand Task
Management and click External Application Launch.
2. On the External Application Launch page, click Refresh. The list of available
external applications is refreshed.

Note: Restarting the IBM Systems Director Server also refreshes the list of
external-application tasks.

196 IBMSystems Director Systems Management Guide

Related concepts
External-application tasks
Related tasks
“Creating a command-task file” on page 193
“Specifying national-language task titles” on page 193
Configuring external-application tasks for browser systems
Starting external-application tasks in the IBM Systems Director Web interface
“Deleting an external-application task” on page 198
Related reference
“Command-task file location and naming conventions” on page 180
“Command-task file parameters” on page 181
“Considerations for command-string parameters” on page 188

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.

Chapter 2. Using the Web interface 197

 Related concepts
External-application tasks
Related tasks
“Refreshing external-application tasks in the IBM Systems Director Web interface”
on page 196
“Creating a command-task file” on page 193
“Specifying national-language task titles” on page 193
Configuring external-application tasks for browser systems
“Deleting an external-application task”
Related reference
“Command-task file location and naming conventions” on page 180
“Command-task file parameters” on page 181
“Considerations for command-string parameters” on page 188

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.

198 IBMSystems Director Systems Management Guide

 Related concepts
External-application tasks
Related tasks
“Refreshing external-application tasks in the IBM Systems Director Web interface”
on page 196
“Creating a command-task file” on page 193
“Specifying national-language task titles” on page 193
Configuring external-application tasks for browser systems
Starting external-application tasks in the IBM Systems Director Web interface
Related reference
“Command-task file location and naming conventions” on page 180
“Command-task file parameters” on page 181
“Considerations for command-string parameters” on page 188

Scheduling tasks
You can use Scheduler (also called the Run 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: Navigating in IBM Systems Director
“Launched tasks and the IBM Systems Director Launched Tasks program” on page
161
eLearning: Scheduling tasks
Related tasks
“Navigating IBM Systems Director by way of the Welcome page” on page 80
“Finding and navigating resources” on page 95
“Finding and starting tasks” on page 161
“Starting tasks” on page 163
“Navigating the Web interface” on page 76
“Managing groups” on page 146
“Removing all process monitors” on page 327
Related reference
lsgp command
accesssys command
runtask command
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.

Chapter 2. Using the Web interface 199

 Related concepts
“Jobs and job instances”
Related tasks
“Scheduling a task” on page 201
“Scheduling a task from a selected system” on page 203
“Viewing active and scheduled job information” on page 205
“Viewing information about scheduled jobs” on page 207
“Determining target systems that are affected by a job” on page 208
“Viewing job-instance records” on page 209
“Viewing job-instance logs” on page 210
“Copying a scheduled job” on page 212
“Editing a scheduled job” on page 213
“Running a scheduled job immediately” on page 214
“Suspending and resuming a scheduled job” on page 215
“Deleting a job” on page 216

Jobs and job instances

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.

200 IBMSystems Director Systems Management Guide

 Related concepts
“Noninteractive tasks” on page 199
Related tasks
“Scheduling a task”
“Scheduling a task from a selected system” on page 203
“Viewing active and scheduled job information” on page 205
“Viewing information about scheduled jobs” on page 207
“Determining target systems that are affected by a job” on page 208
“Viewing job-instance records” on page 209
“Viewing job-instance logs” on page 210
“Copying a scheduled job” on page 212
“Editing a scheduled job” on page 213
“Running a scheduled job immediately” on page 214
“Suspending and resuming a scheduled job” on page 215
“Deleting a job” on page 216

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 Run window is
not displayed. For more information, see “Noninteractive tasks.”
3. The Run 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 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
on 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.”

Chapter 2. Using the Web interface 201

 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 e-mail notification is
sent. You can specify that the e-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 e-mail address, e-mail server, and e-mail server port.

Tip: You can provide only one e-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 Run 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 Run window so that you can correct the job.

The job is displayed on the Active and Scheduled Jobs page.

202 IBMSystems Director Systems Management Guide

 Related concepts
“Noninteractive tasks” on page 199
“Jobs and job instances” on page 200
Related tasks
“Scheduling a task from a selected system”
“Viewing active and scheduled job information” on page 205
“Viewing information about scheduled jobs” on page 207
“Determining target systems that are affected by a job” on page 208
“Viewing job-instance records” on page 209
“Viewing job-instance logs” on page 210
“Copying a scheduled job” on page 212
“Editing a scheduled job” on page 213
“Running a scheduled job immediately” on page 214
“Suspending and resuming a scheduled job” on page 215
“Deleting a job” on page 216
Related reference
lsjob command
lsjobhistory command
rmjobhistory command
runjob command
rmjob command

Scheduling a task from a selected system

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 Navigate Resources 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
Run 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 Run window is not displayed. For more information, see “Noninteractive
tasks.”
3. The Run 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.
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 on page 202.
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.

Chapter 2. Using the Web interface 203

 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.
5. 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 e-mail notification is
sent. You can specify that the e-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 e-mail address, e-mail server, and e-mail server port.

Tip: You can provide only one e-mail address.

6. 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.
7. Click OK to save the job.
Click Cancel to exit from the Run 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 Run window so that you can correct the job.

The job is displayed on the Active and Scheduled Jobs page.

204 IBMSystems Director Systems Management Guide

 Related concepts
“Noninteractive tasks” on page 199
“Jobs and job instances” on page 200
Related tasks
“Scheduling a task” on page 201
“Viewing active and scheduled job information”
“Viewing information about scheduled jobs” on page 207
“Determining target systems that are affected by a job” on page 208
“Viewing job-instance records” on page 209
“Viewing job-instance logs” on page 210
“Copying a scheduled job” on page 212
“Editing a scheduled job” on page 213
“Running a scheduled job immediately” on page 214
“Suspending and resuming a scheduled job” on page 215
“Deleting a job” on page 216
Related reference
lsjob command
lsjobhistory command
rmjobhistory command
runjob command
rmjob command

Viewing active and scheduled job information

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

Chapter 2. Using the Web interface 205

 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.

206 IBMSystems Director Systems Management Guide

 Related concepts
“Noninteractive tasks” on page 199
“Jobs and job instances” on page 200
“Discovery” on page 231
“Discovery protocols” on page 232
“System discovery” on page 237
“Inventory data and collection profiles” on page 259
Related tasks
“Scheduling a task” on page 201
“Scheduling a task from a selected system” on page 203
“Viewing information about scheduled jobs”
“Determining target systems that are affected by a job” on page 208
“Viewing job-instance records” on page 209
“Viewing job-instance logs” on page 210
“Copying a scheduled job” on page 212
“Editing a scheduled job” on page 213
“Running a scheduled job immediately” on page 214
“Suspending and resuming a scheduled job” on page 215
“Deleting a job” on page 216
“Performing an advanced system discovery” on page 48
“Collecting inventory” on page 68
Related reference
lsjob command
lsjobhistory command
rmjobhistory command
runjob command
rmjob command

Viewing information about scheduled jobs

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:

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, 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.
v The date that the job last ran.
v The date that the job will run next.

Chapter 2. Using the Web interface 207

 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
“Noninteractive tasks” on page 199
“Jobs and job instances” on page 200
Related tasks
“Scheduling a task” on page 201
“Scheduling a task from a selected system” on page 203
“Viewing active and scheduled job information” on page 205
“Determining target systems that are affected by a job”
“Viewing job-instance records” on page 209
“Viewing job-instance logs” on page 210
“Copying a scheduled job” on page 212
“Editing a scheduled job” on page 213
“Running a scheduled job immediately” on page 214
“Suspending and resuming a scheduled job” on page 215
“Deleting a job” on page 216
Related reference
lsjob command
lsjobhistory command
rmjobhistory command
runjob command
rmjob command

Determining target systems that are affected by a job

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:

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, select the job that you want to view
and click Actions → Properties.
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.
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.

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.

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.

208 IBMSystems Director Systems Management Guide

 Related concepts
“Noninteractive tasks” on page 199
“Jobs and job instances” on page 200
Related tasks
“Scheduling a task” on page 201
“Scheduling a task from a selected system” on page 203
“Viewing active and scheduled job information” on page 205
“Viewing information about scheduled jobs” on page 207
“Viewing job-instance records”
“Viewing job-instance logs” on page 210
“Copying a scheduled job” on page 212
“Editing a scheduled job” on page 213
“Running a scheduled job immediately” on page 214
“Suspending and resuming a scheduled job” on page 215
“Deleting a job” on page 216
Related reference
lsjob command
lsjobhistory command
rmjobhistory command
runjob command
rmjob command

Viewing job-instance records

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:

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, select the job that you want to view
and click Actions → Properties.
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.

Chapter 2. Using the Web interface 209

 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.
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
“Noninteractive tasks” on page 199
“Jobs and job instances” on page 200
Related tasks
“Scheduling a task” on page 201
“Scheduling a task from a selected system” on page 203
“Viewing active and scheduled job information” on page 205
“Viewing information about scheduled jobs” on page 207
“Determining target systems that are affected by a job” on page 208
“Viewing job-instance logs”
“Copying a scheduled job” on page 212
“Editing a scheduled job” on page 213
“Running a scheduled job immediately” on page 214
“Suspending and resuming a scheduled job” on page 215
“Deleting a job” on page 216
Related reference
lsjob command
lsjobhistory command
rmjobhistory command
runjob command
rmjob command

Viewing job-instance logs

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:

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, select the job that you want to view
and click Actions → Properties.

210 IBMSystems Director Systems Management Guide

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.
Complete with 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.
5. 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.

Chapter 2. Using the Web interface 211

 Related concepts
“Noninteractive tasks” on page 199
“Jobs and job instances” on page 200
Related tasks
“Scheduling a task” on page 201
“Scheduling a task from a selected system” on page 203
“Viewing active and scheduled job information” on page 205
“Viewing information about scheduled jobs” on page 207
“Determining target systems that are affected by a job” on page 208
“Viewing job-instance records” on page 209
“Copying a scheduled job”
“Editing a scheduled job” on page 213
“Running a scheduled job immediately” on page 214
“Suspending and resuming a scheduled job” on page 215
“Deleting a job” on page 216
Related reference
lsjob command
lsjobhistory command
rmjobhistory command
runjob command
rmjob command

Copying a scheduled job

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:

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, 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.

212 IBMSystems Director Systems Management Guide

 Related concepts
“Noninteractive tasks” on page 199
“Jobs and job instances” on page 200
Related tasks
“Scheduling a task” on page 201
“Scheduling a task from a selected system” on page 203
“Viewing active and scheduled job information” on page 205
“Viewing information about scheduled jobs” on page 207
“Determining target systems that are affected by a job” on page 208
“Viewing job-instance records” on page 209
“Viewing job-instance logs” on page 210
“Editing a scheduled job”
“Running a scheduled job immediately” on page 214
“Suspending and resuming a scheduled job” on page 215
“Deleting a job” on page 216
Related reference
lsjob command
lsjobhistory command
rmjobhistory command
runjob command
rmjob command

Editing a scheduled job

Edit a job to change its settings. You can edit only jobs that have not run. If a job
has run once or more, you cannot edit it.

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.

To edit a scheduled job, 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, 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.

Chapter 2. Using the Web interface 213

 Related concepts
“Noninteractive tasks” on page 199
“Jobs and job instances” on page 200
Related tasks
“Scheduling a task” on page 201
“Scheduling a task from a selected system” on page 203
“Viewing active and scheduled job information” on page 205
“Viewing information about scheduled jobs” on page 207
“Determining target systems that are affected by a job” on page 208
“Viewing job-instance records” on page 209
“Viewing job-instance logs” on page 210
“Copying a scheduled job” on page 212
“Running a scheduled job immediately”
“Suspending and resuming a scheduled job” on page 215
“Deleting a job” on page 216
Related reference
lsjob command
lsjobhistory command
rmjobhistory command
runjob command
rmjob command

Running a scheduled job immediately

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:

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, 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.

214 IBMSystems Director Systems Management Guide

 Related concepts
“Noninteractive tasks” on page 199
“Jobs and job instances” on page 200
Related tasks
“Scheduling a task” on page 201
“Scheduling a task from a selected system” on page 203
“Viewing active and scheduled job information” on page 205
“Viewing information about scheduled jobs” on page 207
“Determining target systems that are affected by a job” on page 208
“Viewing job-instance records” on page 209
“Viewing job-instance logs” on page 210
“Copying a scheduled job” on page 212
“Editing a scheduled job” on page 213
“Suspending and resuming a scheduled job”
“Deleting a job” on page 216
Related reference
lsjob command
lsjobhistory command
rmjobhistory command
runjob command
rmjob command

Suspending and resuming a scheduled job

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 a job instance that is currently running. 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:

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, select the job that you want to edit.
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.

Chapter 2. Using the Web interface 215

 Related concepts
“Noninteractive tasks” on page 199
“Jobs and job instances” on page 200
Related tasks
“Scheduling a task” on page 201
“Scheduling a task from a selected system” on page 203
“Viewing active and scheduled job information” on page 205
“Viewing information about scheduled jobs” on page 207
“Determining target systems that are affected by a job” on page 208
“Viewing job-instance records” on page 209
“Viewing job-instance logs” on page 210
“Copying a scheduled job” on page 212
“Editing a scheduled job” on page 213
“Running a scheduled job immediately” on page 214
“Deleting a job”
Related reference
lsjob command
lsjobhistory command
rmjobhistory command
runjob command
rmjob command

Deleting a job
Delete a existing job when you no longer need it.

To delete a job, 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, 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.

216 IBMSystems Director Systems Management Guide

 Related concepts
“Noninteractive tasks” on page 199
“Jobs and job instances” on page 200
Related tasks
“Scheduling a task” on page 201
“Scheduling a task from a selected system” on page 203
“Viewing active and scheduled job information” on page 205
“Viewing information about scheduled jobs” on page 207
“Determining target systems that are affected by a job” on page 208
“Viewing job-instance records” on page 209
“Viewing job-instance logs” on page 210
“Copying a scheduled job” on page 212
“Editing a scheduled job” on page 213
“Running a scheduled job immediately” on page 214
“Suspending and resuming a scheduled job” on page 215
Related reference
lsjob command
lsjobhistory command
rmjobhistory command
runjob command
rmjob command

Managing auditing
With the auditing capabilities, you can track what takes place on IBM Systems
Director Server. Use 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 log audit settings, view audit
log files, and delete audit log files.

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, configuration changes, and the status of user creation, deletion,
and modification.

Consider this sample audit record from the command-line interface category:
Jul 17 2007 9:04:20 AM, Command line interface, , , IBM Director CLI Command Failed, CLI Command [mkgp -n
cs9..44.146.1;cs9.44.146.129 Group101] failed with error code [20], aomar, localhost, ,

Using this audit record as an example, the following table shows the information
that makes up an audit record.

Note: The last five information slots are the message field of the audit record. The
contents of these slots are whatever the component requires. The component uses
the Java messageFormat routine to format the text.
Table 16. Audit-record information
Information type Example
Date and time Jul 17 2007 9:04:20 AM,

Chapter 2. Using the Web interface 217

 Table 16. Audit-record information (continued)
Information type Example
Category Command line interface,
Name of the class that generated the ,
message
Note: This information is in a national
language file that can be translated. If it is
not in the file, this information type is
empty and a comma delimiter is present.
Name of the method that generated the ,
message
Note: This information is in a national
language file that can be translated. If it is
not in the file, this information type is
empty and a comma delimiter is present.
Audit record IBM Director CLI Command Failed,
Failure details CLI Command [mkgp -n
cs9..44.146.1;cs9.44.146.129 Group101] failed
with error code [20],
User aomar,
System localhost,
Unused information slot ,
Note: This slot was not used by the class
that generated the message. The information
type is empty and a comma delimiter is
present.

IBM Systems Director provides several categories of audit records.

Related tasks
“Setting server-auditing preferences” on page 223
“Viewing the audit log” on page 225
“Deleting the audit log” on page 225

Command-line interface audit records

When this category is selected, audit records are logged for the running and failure
of command-line interface (CLI) commands.

Note: When you select a category to audit, you will receive audit records for
significant changes, but not for every change that occurs.

The audit records can include the following data:

v Command was executed successfully
v Command was not executed successfully

The following output is an example of command-line interface audit-log

information:
Jul 17 2007 9:04:20 AM, Command line interface, , , IBM Director CLI Command Failed, CLI Command [mkgp -n
cs9..44.146.1;cs9.44.146.129 Group101] failed with error code [20], aomar, localhost, ,

218 IBMSystems Director Systems Management Guide

Related concepts
“Configuration-changes audit records”
“File-read audit records”
“File-write audit records” on page 220
“Remote-access audit records” on page 220
“Remote-command execution audit records” on page 221
“Security audit records” on page 221
“Task activation and deactivation audit records” on page 222
“User-administration audit records” on page 222

Configuration-changes audit records

When this category is selected, audit records are logged for actions such as a
restart of the network configuration, an asset configuration change, an SNMP
configuration change, or an Alert-Standard Format (ASF) configuration change.

Note: When you select a category to audit, you will receive audit records for
significant changes, but not for every change that occurs.

The audit records can include the following data:

v Change network configuration (such as TCP/IP addresses and DNS servers)
v Restart due to network configuration changes
v Change SNMP configuration
v Change asset information
v Mass Configuration profile added, removed, or changed on a system or group
Related concepts
“Command-line interface audit records” on page 218
“File-read audit records”
“File-write audit records” on page 220
“Remote-access audit records” on page 220
“Remote-command execution audit records” on page 221
“Security audit records” on page 221
“Task activation and deactivation audit records” on page 222
“User-administration audit records” on page 222

File-read audit records

When this category is selected, audit records are logged for actions such as
transferring a file.

Note: When you select a category to audit, you will receive audit records for
significant changes, but not for every change that occurs.

The audit records can include data for viewing a file. This file is audited only if the
file that is read is on IBM Systems Director Server and IBM Systems Director
Server is not running on Windows.

Note: If IBM Systems Director Server is running on Windows, file transfer is not
audited.

Chapter 2. Using the Web interface 219

 Related concepts
“Command-line interface audit records” on page 218
“Configuration-changes audit records” on page 219
“File-write audit records”
“Remote-access audit records”
“Remote-command execution audit records” on page 221
“Security audit records” on page 221
“Task activation and deactivation audit records” on page 222
“User-administration audit records” on page 222

File-write audit records

When this category is selected, audit records are logged for actions such as
transferring a file, deleting a file or directory, creating a directory, or renaming a
file.

Note: When you select a category to audit, you will receive audit records for
significant changes, but not for every change that occurs.

The audit records can include the following data. This data is audited only if the
file written is on IBM Systems Director Server and IBM Systems Director Server is
not running on Windows.
v Add or change a file (audited as File Transfer to IBM Systems Director Server)

Note: If IBM Systems Director Server is running on Windows, file transfer is not
audited.
v Rename a file
v Delete a file
v Transfer a file
v Rename a directory
v Delete a directory
v Add a directory
Related concepts
“Command-line interface audit records” on page 218
“Configuration-changes audit records” on page 219
“File-read audit records” on page 219
“Remote-access audit records”
“Remote-command execution audit records” on page 221
“Security audit records” on page 221
“Task activation and deactivation audit records” on page 222
“User-administration audit records” on page 222

Remote-access audit records

When this category is selected, audit records are logged for actions such as remote
control sessions, the start of a remote session, or the end of a remote session.

Note: When you select a category to audit, you will receive audit records for
significant changes, but not for every change that occurs.

The audit records can include the following data:

v Start a remote session
v End a remote session
v Start a remote control session

220 IBMSystems Director Systems Management Guide

v End a remote control session
Related concepts
“Command-line interface audit records” on page 218
“Configuration-changes audit records” on page 219
“File-read audit records” on page 219
“File-write audit records” on page 220
“Remote-command execution audit records”
“Security audit records”
“Task activation and deactivation audit records” on page 222
“User-administration audit records” on page 222

Remote-command execution audit records

When this category is selected, audit records are logged to track whether a
command succeeded or failed.

Note: When you select a category to audit, you will receive audit records for
significant changes, but not for every change that occurs.

The audit records can include data for running a remote command using a Process
task.

Note: Running a command from the Command Automation page by selecting a

command definition and clicking Run does not generate an audit record in the
audit log.
Related concepts
“Command-line interface audit records” on page 218
“Configuration-changes audit records” on page 219
“File-read audit records” on page 219
“File-write audit records” on page 220
“Remote-access audit records” on page 220
“Security audit records”
“Task activation and deactivation audit records” on page 222
“User-administration audit records” on page 222

Security audit records

When this category is selected, audit records are logged for actions such as the
logging on of a user, the logging off of a user, enabling Secure Socket Layer (SSL),
disabling SSL, enabling encryption, and disabling encryption.

Note: When you select a category to audit, you will receive audit records for
significant changes, but not for every change that occurs.

The audit records can include the following data:

v SSL turned on
v SSL turned off
v Encryption turned on (not audited on management servers running on
Windows)
v Encryption turned off (not audited on management server running on Windows)
v Request Access to Agent successful
v Request Access to Agent unsuccessful
v Director User Administration privileges altered
v Successful login

Chapter 2. Using the Web interface 221

 v Successful logout
v Unsuccessful login
v Auditing settings changed

The following output is an example of security audit-log information:

Jul 17 2007 9:04:17 AM, Security, , , User Logon, , aomar, localhost, ,
Jul 17 2007 9:04:20 AM, Security, , , User Logoff, , aomar, localhost, , Logged out 2891 seconds after
logging in

Related concepts
“Command-line interface audit records” on page 218
“Configuration-changes audit records” on page 219
“File-read audit records” on page 219
“File-write audit records” on page 220
“Remote-access audit records” on page 220
“Remote-command execution audit records” on page 221
“Task activation and deactivation audit records”
“User-administration audit records”

Task activation and deactivation audit records

When this category is selected, audit records are logged when IBM Systems
Director tasks start or end.

Note: When you select a category to audit, you will receive audit records for
significant changes, but not for every change that occurs.

The audit records can include the following data:

v Task activated
v Task deactivated
v Task scheduled
Related concepts
“Command-line interface audit records” on page 218
“Configuration-changes audit records” on page 219
“File-read audit records” on page 219
“File-write audit records” on page 220
“Remote-access audit records” on page 220
“Remote-command execution audit records” on page 221
“Security audit records” on page 221
“User-administration audit records”

User-administration audit records

If this category is selected for auditing, audit records are written to the audit log
for actions such as creating a user, deleting a user, or modifying a user.

Note: When you select a category to audit, you will receive audit records for
significant changes, but not for every change that occurs.

The audit records can include data about the following actions:
v Create a user or group on an agent system
v Delete a user or group on an agent system
v Modify a user or group on an agent system
v Add or remove users from a group on an agent system

222 IBMSystems Director Systems Management Guide

 Related concepts
“Command-line interface audit records” on page 218
“Configuration-changes audit records” on page 219
“File-read audit records” on page 219
“File-write audit records” on page 220
“Remote-access audit records” on page 220
“Remote-command execution audit records” on page 221
“Security audit records” on page 221
“Task activation and deactivation audit records” on page 222

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, what types
of audit records to log, the maximum file for an audit log, and how many of the
preceding audit log files to save after a new audit log file is started. 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, configuration changes, and the status of user creation, deletion, and
modification.

Note: Server auditing is disabled by default.

To set the server auditing preferences for IBM Systems Director Server, complete
the following steps:
1. In the IBM Systems Director Web interface navigation area, expand Settings
and click Server Auditing.
2. On the Server Auditing page, select Enable auditing. If you want to disable
auditing, clear the 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.

Note: If you are enabling auditing for the first time, all of the categories are
selected for auditing by default.

You can select from the following auditing categories. For more information
about the audit categories, see “Audit records.”

Note: When you select a category to audit, you will receive audit records for
significant changes, but not for every change that occurs.
Configuration changes
When this category is selected, audit records are logged for actions
such as a restart of the network configuration, an asset configuration
change, an SNMP configuration change, or an Alert-Standard Format
(ASF) configuration change.
Command line interface
When this category is selected, audit records are logged for the running
and failure of command-line interface (CLI) commands.
File read
When this category is selected, audit records are logged for actions
such as transferring a file.

Chapter 2. Using the Web interface 223

 Note: If IBM Systems Director Server is running on Windows, file
transfer is not audited.
File write
When this category is selected, audit records are logged for actions
such as transferring a file, deleting a file or directory, creating a
directory, or renaming a file.

Note: If IBM Systems Director Server is running on Windows, file

transfer is not audited.
Remote access
When this category is selected, audit records are logged for actions
such as remote control sessions, the start of a remote session, or the end
of a remote session.
Remote command execution
When this category is selected, audit records are logged to track
whether a command succeeded or failed.

Note: Running a command from the Command Automation page by

selecting a command definition and clicking Run does not generate an
audit record in the audit log.
Security
When this category is selected, audit records are logged for actions
such as the logging on of a user, the logging off of a user, enabling
Secure Socket Layer (SSL), disabling SSL, enabling encryption, and
disabling encryption.

Note: If IBM Systems Director Server is running on Windows, enabling

and disabling encryption is not audited.
Task activation/deactivation
When this category is selected, audit records are logged when IBM
Systems Director tasks start or end.
User create/delete/modify
If this category is selected for auditing, audit records are written to the
audit log for actions such as creating a user, deleting a user, or
modifying a user.
4. Specify the number of files to use for audit logs and the maximum size for each
file. You cannot change the name of audit files. The audit files are named
auditLog_x.txt, where x is an integer starting at 0 that increases by one for each
subsequent file. The path for the current audit file is displayed.
When determining the audit log file settings, consider the following
information:
v The default setting for the maximum size of a log file is 512 MB. The
maximum setting permitted is 2000 MB. When the size of an audit file
reaches this setting, it is saved and a new file is started. Files are saved in the
log directory in the installation location for IBM Systems Director Server.
v The default setting for the number of audit log files is 8. The maximum
setting permitted is 99.
5. 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. To reset the settings to the
system-defined values, click Restore Defaults. You still must click OK or
Apply to save the restored settings.

224 IBMSystems Director Systems Management Guide

 For information about viewing audit logs, see “Viewing the audit log.”
Related concepts
“Audit records” on page 217
Related tasks
“Viewing the audit log”
“Deleting 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 text format and can be viewed in text editors or Web
browsers.

To view the audit log when auditing is enabled, complete the following steps:
1. In the IBM Systems Director Web interface navigation area, expand Settings
and click Server Auditing.
2. On the Server Auditing page, select the log file that you want to view from the
Saved logs list at the bottom of the page. Then, click View Audit Log.
3. An additional Web browser window opens and prompts you to either open the
audit log file in the Web browser or save the log file to your local system.
Related concepts
“Audit records” on page 217
Related tasks
“Setting server-auditing preferences” on page 223
“Deleting the audit log”

Deleting the audit log

Use Server Auditing to delete the audit logs.

Attention: Audit files are not saved or archived automatically. Deleting the audit
log is a task that cannot be undone.

To delete the audit log, complete the following steps:

1. In the IBM Systems Director Web interface navigation area, expand Settings
and click Server Auditing.
2. On the Server Auditing page, click Delete All Logs to delete all log files.
3. A confirmation window is displayed. Click Delete to confirm deleting all log
files.

Chapter 2. Using the Web interface 225

 Related concepts
“Audit records” on page 217
Related tasks
“Setting server-auditing preferences” on page 223
“Viewing the audit log” on page 225

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.

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.

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.

226 IBMSystems Director Systems Management Guide

Table 17. 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.

Chapter 2. Using the Web interface 227

 Related tasks
“Enabling encryption”
“Disabling encryption”
“Changing the encryption algorithm” on page 229
“Resending the encryption key to systems” on page 229
“Creating a new encryption key” on page 230
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.

To enable encryption on IBM Director Agent, versions 5.20.3 and earlier, complete
the following steps:
1. In the IBM Systems Director Web interface navigation area, expand Settings
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” on page 226
Related tasks
“Disabling encryption”
“Changing the encryption algorithm” on page 229
“Resending the encryption key to systems” on page 229
“Creating a new encryption key” on page 230
Related reference
System commands

Disabling encryption
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.

To disable encryption on IBM Director Agent, versions 5.20.3 and earlier, complete
the following steps:
1. In the IBM Systems Director Web interface navigation area, expand Settings
and click Encryption Preferences.
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.

228 IBMSystems Director Systems Management Guide

 5. A confirmation message is displayed. Click OK to save the change and close
the page.
Related concepts
“Encryption” on page 226
Related tasks
“Enabling encryption” on page 228
“Changing the encryption algorithm”
“Resending the encryption key to systems”
“Creating a new encryption key” on page 230
Related reference
System commands

Changing the encryption algorithm

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.

To change the encryption algorithm for systems running IBM Director Agent,
versions 5.20.3 and earlier, complete the following steps:
1. In the IBM Systems Director Web interface navigation area, expand Settings
and click Encryption Preferences.
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” on page 226
Related tasks
“Enabling encryption” on page 228
“Disabling encryption” on page 228
“Resending the encryption key to systems”
“Creating a new encryption key” on page 230
Related reference
System commands

Resending the encryption key to systems

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.

To resend encryption keys to all systems running IBM Director Agent, versions
5.20.3 and earlier, complete the following steps:

Chapter 2. Using the Web interface 229

 1. In the IBM Systems Director Web interface navigation area, expand Settings
and click Encryption Preferences.
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” on page 226
Related tasks
“Enabling encryption” on page 228
“Disabling encryption” on page 228
“Changing the encryption algorithm” on page 229
“Creating a new encryption key”
Related reference
System commands

Creating a new encryption key

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.

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 Navigate
Resources.
2. On the Navigate Resources 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” on page 226
Related tasks
“Enabling encryption” on page 228
“Disabling encryption” on page 228
“Changing the encryption algorithm” on page 229
“Resending the encryption key to systems” on page 229
Related reference
System commands

230 IBMSystems Director Systems Management Guide

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.
Related concepts
“Discovery manager” on page 10
“Manageable resource types” on page 7
“Manageable systems” on page 7
Related tasks
“Discovering and collecting inventory for storage devices” on page 590

Discovery
Discovery is the process by which IBM Systems Director Server identifies and
establishes connections with network-level resources, such as computers, switches,
or printers, that IBM Systems Director can manage. You can use system discovery
or advanced system discovery to identify resources within your environment,
collect data about the resources, and establish connections with the resource.

Before you can use IBM Systems Director to manage a device, that resource must
be discovered by IBM Systems Director Server. After a resource has been
discovered, it becomes a system that can be managed by IBM Systems Director.

There are two tasks that you can use to discover your systems:
System discovery
Use this task if you want to discover systems at a specific network address
or range of addresses.
Advanced system discovery
Use this task if you want to discover a specific type of resource or schedule
a discovery task.

After a system has been discovered, it is displayed on the Navigate Resources

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 Start tab of the Welcome page. The discovery section
provides the following tasks and information:
v The Discover button, which launches the task that you use to perform initial
discovery in your systems-management environment.
v A pie chart and corresponding list that indicate the number of resources that
were found, broken down into the following three categories:
– Systems with no agent (agentless)

© Copyright IBM Corp. 1999, 2009 231

 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 resources in that
category.
v The number of resources to which you do not have access.
v The number of resources on which inventory has not been collected.
v In the Optional tasks area, the following links are provided:
– Click Systems Discovery to open the systems discovery task, with which you
can discover systems at a specific network address or range of addresses.
– Click Advanced Systems Discovery to open the advanced systems discovery
task, with which you can discover a specific type of resource or schedule a
discovery task.
– Click View and collect 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.
– Click Navigate resources to open the navigate resources task, with which you
can view and manage discovery options on an individual resource level.
Related concepts
“Manageable systems” on page 7
Related tasks
“Collecting inventory” on page 68
“Creating a discovery profile” on page 34

Discovery protocols
During system discovery, IBM Systems Director Server attempts to communicate
with target resources by using a predetermined list of protocols. When using
advanced system discovery, IBM Systems Director Server attempts to communicate
with target resources by using only the protocols that you have configured.

IBM Systems Director Server can be used to discover network-level resources that
use a communication protocol that is supported by the IBM Systems Director
discovery process. The protocol that is used to discover a specific type of resource
depends on the communication protocol used by that resource.

A discovery protocol is any network communication protocol that is used by IBM

Systems Director during the discovery process to discover a system. 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.

232 IBMSystems Director Systems Management Guide

 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
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.

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, inventory data,
system access, and system authentication. Note that information on the summary
page is refreshed automatically when there are any changes.

To view the discovery manager summary, complete the following steps:

1. In the IBM Systems Director navigation area, click Welcome.
2. On the Welcome page, click the Manage tab. A list of available summary pages
is displayed.

Chapter 3. Discovering systems and collecting inventory data 233

 3. On the Manage 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: If a system has not been discovered, it will not show up anywhere on
this page.
v In the Common tasks area, the following links are provided:
Advanced System Discovery
Use the Advanced System Discovery page to discover a specific type
of resource or schedule a discovery task.
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.
Navigate resources
Use the Navigate Resources page to view and manage discovery
options on an individual resource level.
5. View the Access and Authentication section. This section provides the
following information:
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.
Systems with full access
IBM Systems Director is fully authenticated and, barring other
inhibitors, able to perform tasks on these systems.

Click any of the category list items to see a breakdown of the systems in that
category.
v In the Common tasks area, the following links are provided:
Request access for ’no access’ systems
Use the Request access for ’no access’ systems page to view a list of
systems that are in the no access state and request, with a user ID
and password, access for any of those systems.
Manage Credentials
Use the Manage Credentials page to manage all your shared
credentials.

234 IBMSystems Director Systems Management Guide

 You also can reach the summary page by using Find a Task. For more information,
see “Finding a task.”
Related tasks
“Finding a task” on page 162
“Accessing a secured system with request access” on page 714
“Managing credentials in IBM Systems Director” on page 704

Performing initial discovery

Use the Discover button on the Welcome page to perform initial discovery of the
systems in your local subnet.

After you install IBM Systems Director and start the IBM Systems Director Web
interface for the first time, you are presented with a Discover button on the Start
tab of the Welcome page. Use the associated task to perform agent-based discovery
on only your local subnet and, optionally, request access to the systems that are
discovered.

You can perform initial discovery only once for every IBM Systems Director
installation.

To perform initial discovery, complete the following steps:

1. Launch the IBM Systems Director Web interface and click on the Start tab of
the Welcome page.
2. Click Discover. The Discover Network page is displayed.
3. Choose either of the following methods to request access to the discovered
systems:
Use user ID and password
Prompts you for a user ID and password that is then used to request
access to all the discovered systems. Access is granted to those systems
that accept the provided credentials.
Request access later
Discovers the systems but does not attempt to request access to any of
them. You can then use the request access tasks provided by IBM
Systems Director to manually request access at a later time.
4. Click Discover. A status icon displays the status of the system discovery, and
the dynamic elements on the page (for example, the pie chart) change to reflect
the current statistics of the set of discovered resources.

Note: You will see Discovery completed in place of the Discover button after
all the discovery requests are sent. However, systems will continue to appear
after that as they respond to the discovery request and manageable objects are
created.

After discovery is completed, use the navigate resources task to view and work
with the resources.

Chapter 3. Discovering systems and collecting inventory data 235

 Related concepts
The Start page
The Manage page
The Learn page
Related tasks
“Accessing a secured system with request access” on page 714
“Finding and navigating resources” on page 95

Renaming discovered systems automatically

Following discovery, IBM Systems Director assigns a name to each discovered
system that might be cryptic and unsuitable. To help you better organize your
systems and ensure consistency among system names, it is often beneficial to
rename each system to follow a certain convention. You can accomplish this task
for each individual system in Navigate Resources, which becomes laborious when
you have a large number of discovered systems, or you can configure IBM Systems
Director to automatically rename each discovered system to a name that matches a
specified, predefined template.

To automatically rename discovered systems, complete the following steps:

1. In the IBM Systems Director Web interface navigation area, expand Settings
and then click Auto Rename. The Auto Rename page, which contains a list of
resource types and any associated rename templates, is displayed.
2. On the Auto Rename page, select the profile that you want to configure for
automatic renaming.
3. Click Edit. The Edit Template page is displayed.
4. Use the Edit Template page to specify the convention (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 hardcoded text to be inserted into the name template,

select %TEXT%.
b. Click Insert.
c. Select each subsequent variable and click Insert after each one.
d. If you need to restore the default template value to the input field, click
Reset template to defaults.
e. Enable the application of the template to the name of each system after it is
discovered by selecting Yes.
5. When you are finished with the Edit Template page, click OK. The template
that you specified will be displayed in the table.
6. Click Rename. The Run - AutoRename page is displayed.
7. Use the Run - AutoRename page to set up targets and options for your auto
rename task:
Targets
Use the Targets page to add to the template the targets on which the
auto rename task will run:
a. In the Show menu, select All Targets to add individual resources or
Groups to add group of resources.

236 IBMSystems Director Systems Management Guide

 b. Select the targets that you want to add
c. Click Add.
d. Continue selecting targets and adding them as needed.
All the selected targets will be renamed upon execution of the task.
Schedule
Use the Schedule page to set the auto rename 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 page to choose options for an email notification
that you can receive as the auto rename process progresses.
Options
Use the Options page to specify the time to use for the system time and
how to handle unavailable systems.
8. When you are finished with the Run - AutoRename page, click OK. The auto
rename task will either run or be scheduled to run.
Related concepts
“Discovery profiles” on page 239

Discovering systems with system discovery

Use the System Discovery task to identify systems at a specific network address or
range of addresses.
Related tasks
“Collecting and viewing inventory data” on page 259

System discovery
To discover systems at a specific network address or range of addresses, use
system discovery. This method is useful in networks in which both broadcast and
multicast messages are filtered.

System discovery discovers Agentless-managed systems, Platform-Agent managed

systems, and Common-Agent managed systems by sending a unicast request to
one or more addresses. IBM Systems Director Server sends one request to each
system at a time.

System discovery provides the following functions:

v Discovery based on a single IP address
v Discovery based on a range of IP addresses
v Discovery based on a host name
After systems are discovered, they are displayed in a table for viewing.

During system discovery, IBM Systems Director Server attempts to communicate

with target resources by using a predetermined list of protocols.

Performing a system discovery

Use the System Discovery task to identify systems at a specific network address or
range of addresses.

To perform a system discovery, complete the following steps:

Chapter 3. Discovering systems and collecting inventory data 237

 1. Open the System Discovery page using either of these two methods:
v On the Welcome page, click System discovery under Optional tasks.
v In the IBM Systems Director Web interface navigation area, expand
Inventory and then click System Discovery.
The System Discovery page is displayed.
2. Select one of the following discovery methods:
Table 18. System discovery methods
To do this task: Complete these steps:
Add a single IP address 1. Click Single system (IP address).
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
resource type list.
Add a range of IP addresses 1. Click Multiple systems (Range of IP
addresses).
2. For the IP address range that contains
the systems that you want to discover,
type the low-end IP address value in the
Starting IP address field and the
high-end IP address value in the Ending
IP address field.
3. If you want to discover only a specific
resource type, select it from the Select
resource type list.
Add a host name of a system 1. Click Single system (Hostname).
2. In the Hostname field, type the host
name of the system that you want to
discover.
3. If you want to discover only a specific
resource type, select it from the Select
resource type list.

3. Click Discover. The Processing discovery protocols message is displayed and

the progress of the discovery process is displayed as a spinning graphic.

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.
4. Optional: If you want to stop the discovery process, click Stop during
discovery.

As systems are discovered, they are displayed in the Discovered Systems table.

Note: After a resource is discovered, the virtual systems that are associated with
that resource are also discovered.

238 IBMSystems Director Systems Management Guide

 Related concepts
“Discovery” on page 231
“Discovery protocols” on page 232
“System discovery” on page 237
“Inventory data and collection profiles” on page 259
Related tasks
“Accessing a secured system with request access” on page 714
“Discovering and collecting inventory for storage devices” on page 590
“Collecting inventory” on page 68

Viewing system discovery results

Use the System Discovery task to view a table that contains the results of all
system discovery tasks as you run them.

To view the system discovery results as you discover systems, complete the
following steps:
1. Open the System Discovery page using either of these two methods:
v On the Welcome page, click System discovery under Optional tasks.
v In the IBM Systems Director Web interface navigation area, expand
Inventory and then click System Discovery.
The System Discovery page is displayed.
2. Discover systems using one of the three available methods.
3. View systems as they are discovered in the Discovered Systems table.

Note: IBM Systems Director Server displays the discovery results for all
discovery requests that occur on the server during your discovery request,
including the results from other IBM Systems Director users who are accessing
the same management server. As a result, the systems that are displayed might
include additional systems that are not located at the target IP addresses or
host names that you enter.

When discovery is completed, all the discovered systems are displayed in the
Discovered Systems table. The table will maintain the information until you exit
the Systems Discovery task, at which point it is cleared.

Discovering systems with advanced system discovery

Use the Advanced System Discovery task to identify specific types of resources or
to schedule a discovery task.
Related tasks
“Collecting and viewing inventory data” on page 259

Discovery profiles
Before performing an advanced system discovery, you must create and configure a
profile that identifies the type of resources that you want to discover and the
discovery protocols that you want to use.

Advanced System Discovery uses discovery profiles to manage the discovery tasks
that you undertake. A discovery profile is a group of discovery settings that are
saved on IBM Systems Director Server that indicate the type of resources
discovered and the communication protocols that are used during the discovery

Chapter 3. Discovering systems and collecting inventory data 239

 process. Using advanced system discovery, you can create, copy, edit, or delete
discovery profiles, run a discovery profile on specific resources, and schedule a
profile to run at specific times or in response to specific events.

Each discovery profile that you create corresponds to one or more types and
subtypes of resources that can be discovered. You can choose from the following
resource types, which are also called system types or profile types, and their
subtypes:
Generic system
The Generic system profile type performs an SNMP-based discovery and
can find any systems, devices, or services not assigned a specific system
type.
Operating system
The Operating system profile type represents the software on the system
and reports the type of agent that is available on that system. The agent
can be either a Common Agent or a Platform Agent. It will also report no
agent, if one is not discovered.
Server The Server profile type discovers a server using its service processor.
These are the type of servers and service processors that can be discovered:
v HMC managing Power Systems
v HMC managing System z
v System x servers with service processors
v IVM managing Power Systems
v Power System servers with service processors
Switch
The Switch profile type performs an SNMP-based discovery of switches
and bridges.
BladeCenter chassis
The BladeCenter chassis profile type represents BladeCenter chassis. A
discovery of this type detects the management module of the chassis.

The following discovery profiles are shipped with IBM Systems Director:
Default CAS discovery
Uses the Common Agent Services (CAS) configuration to discover
Common Agent resources.
Default CIM discovery
Uses the Common Information Model (CIM) configuration to discover
Platform Agent resources.
Default IPC discovery
Uses the Interprocess Communication (IPC) configuration to discover
Common Agent resources.

To discover other resources that have not been included in the configuration of an
existing discovery profile, you can create a new profile specifically for the types of
resources that you want to discover. Use the Advanced Discovery Wizard to
configure or create new profiles.

Depending on the profile type and protocol that you choose, you might need to
perform any of the following tasks when creating a discovery profile:

240 IBMSystems Director Systems Management Guide

Select the agent managers that you want to use for discovery
Specify individual agent managers or select to use all available agent
managers.
Specify the IP address or addresses to query
Input a single IP address, multiple single IP addresses, or a range of IP
addresses. You can also import IP addresses from a line delimited file.
Enable multicast
Choose to use multicast, for which you specify an IP address and timeout
period. When you enable multicast, IBM Systems Director issues an IP
multicast in an attempt to discover service agents. If a directory agent is
provided, then this option is ignored. Multicasting is advantageous because
it has the ability to discover systems across multiple subnets without
requiring specific configuration data for each subnet. Multicast is the
preferred discovery method and is used by default. Not all network
configurations allow multicast.
Enable general broadcast
Choose to use general broadcast. When you enable general broadcast, IBM
Systems Director issues a general IP broadcast to discover service agents. If
a directory agent is provided, then this option is ignored. Some
environments might not allow the use of general IP broadcast to discover
systems, in which case you should not select this option.
Enable directed broadcast
Choose to use directed broadcast, for which you specify an IP address and
subnet mask.
Enable relay broadcast
Choose to use relay broadcast, for which you specify the agent that will
send the broadcast.
Configure directory agents
Use directory agents to configure a proxy using their IP addresses or host
names.
Specify a scope
Specify a scope, which is used to group agents, within which to search for
directory agents. The default scope is DEFAULT.
Configure access request automation
Choose to automatically request access to resources as they are discovered.
Configure inventory discovery automation
Choose to automatically collect inventory from resources as they are
discovered.
Configure SNMP community names
Specify SNMPv1 or SNMPv2c community names for discovery.
Configure SNMP profiles
Create, edit, or delete SNMPv3 profiles.
Configure a direct connection
Configure a direct connection to a hardware resource, specifying the
hardware type, protocol, IPv4 IP address, and port.

Chapter 3. Discovering systems and collecting inventory data 241

 Related tasks
“Managing discovery profiles” on page 256
“Performing an advanced system discovery” on page 48

Creating a discovery profile

From the Advanced System Discovery page, you can create a discovery profile.

To create a discovery profile, complete the following steps:

1. Open the Advanced System Discovery page using either of these two
methods:
v On the Welcome page, click Advanced System Discovery under Optional
tasks.
v In the IBM Systems Director Web interface navigation area, expand
Inventory and then click Advanced System Discovery.
2. On the Advanced System Discovery page, click Create. The Advanced
Discovery Wizard opens and the Welcome page is displayed.
3. Optional: To prevent the Welcome page from displaying the next time you
create a profile, clear Show this Welcome page next time.
4. Click Next. The Profile properties page is displayed.
5. In the Profile name field, type a descriptive name for the profile.
6. From the System type list, select the type of resource that you want to
discover with the profile. The protocols that are available on the next page of
the Advanced Discovery Wizard depend on which profile type is selected
here.
7. Optional: If you want to provide further granularity to your discovery search,
use the System subtype list to select a subtype for the system type that you
previously selected. The default system subtype is All, which will discover all
system subtypes for the selected system type.

Note: The list of system subtypes is dynamically populated based on which

system type you choose.
8. In the Profile description field, type a brief description for the profile.
9. Click Next. The Protocol Selection page is displayed.
10. Select the protocols that you want to use for the discovery profile.

Note: When the profile is run, IBM Systems Director Server uses only the
communication protocols that are saved in the profile. When a profile that
contains multiple protocols is run, the management server sends an IP packet
for each protocol in the profile to every resource that is targeted, which
increases network traffic.
11. Click Next. Complete all pages for each protocol that you selected, clicking
Next on each page to navigate to the next page. Details for each protocol are
as follows:
Agent manager configuration
Select individual agent managers or choose to use all available agent
managers with your profile.
Selecting individual agent managers
In the list of agent managers, select the ones that you want to
use for discovery.

242 IBMSystems Director Systems Management Guide

 Selecting all available agent managers
Select the Use all available agent managers when this profile
is run. option.
Common Agent Services (CAS) configuration
Configure either unicast, multicast and broadcast, or directory agents
to discover your resources. Also activate or deactivate access request
automation and activate or deactivate inventory discovery automation.

Attention: All three discovery methods (unicast, multicast and

broadcast, and directory agents) are presented on this page and you
can provide information for all three at once. However, only one
method at a time will be used to discover resources. For example, if
you fill in all three sections, only the unicast discovery is performed.
The priority for discovery method processing is as follows:
a. Unicast
b. Directory agents
c. Multicast and broadcast
So, if you want to use multiple methods to discover resources, you
must fill out one section, discover those resources, and then return to
fill out another section and discover those other resources.

Note: You cannot configure directory agents for the following profile
types:
v Hardware management console
v Management controller
v Server, when discovering an IVM
Therefore, ensure that you configure multicast and broadcast if you
choose any of those profile types.
When configuring CAS IP addresses, you can add IP addresses either
individually or as a range, or you can import the addresses.
Adding a single IP address
a. Select Add a single IP address.
b. In the Single IP address or beginning range field, type the
IP address of the resource that you want to discover.
c. Click Add to add the IP address to the list.
d. Repeat this procedure until you have added all the IP
addresses.
Adding a range of IP addresses
a. Select Add a range of IP addresses.
b. For the IP address range that contains the resources that
you want to discover, type the low-end IP address value in
the Single IP address or beginning range field and the
high-end IP address value in the Ending range field.
c. Click Add to add the IP addresses to the list.
d. Repeat this procedure until you have added all the IP
addresses.
Importing IP addresses
a. Select Import.
b. In the Select the file that you want to import field, type in
the name of the import file or click Browse to search for
the file.

Chapter 3. Discovering systems and collecting inventory data 243

 Note: Ensure that the file you use is a line delimited file
with one IP address on each line.
c. Click OK to import the IP addresses.
When configuring multicast and broadcast, select to enable either and
set the timeout period.
Enabling multicast
Select Enable multicast to enable multicast.
Setting the timeout period
In the Timeout period (seconds) field, select the number of
seconds that the server will wait until timing out.
Enabling general broadcast
Select Enable general broadcast to enable general broadcast.
When configuring directory agents, specify either an IP address or a
host name and set the scope.
Adding a directory agent using its IP address
a. Select Add IP address.
b. In the IP address field, type the IP address of the directory
agent that you want to discover.
c. Click Add to add the IP address to the list.
d. Repeat this procedure until you have added all the IP
addresses.
Adding a directory agent using its host name
a. Select Add host name.
b. In the Host name field, type the host name of the directory
agent that you want to discover.
c. Click Add to add the host name to the list.
d. Repeat this procedure until you have added all the host
names.
Setting the scope
Each directory agent is associated with a scope. A discovery
request is targeted to find only those directory agents that are
associated with the specified scope. The directory agent
shipped with IBM Systems Director has a default scope of
DEFAULT, so that is the default scope value used when
searching for directory agents. If you want to search for
directory agents with scopes other than DEFAULT, complete
the following steps:
a. In the Scope field, type the name of a scope that you have
defined.
b. Click Add to add the scope to the list.
c. Repeat this procedure until you have added all the scopes.
When setting access request automation, you can choose to deactivate
or activate (with the appropriate login information) the feature.
Activating access request automation
a. Select Activate - use the following user login information.
b. In the User ID field, type a valid user ID for the resource.
c. In the Password field, type the password for the user ID.
Deactivating access request automation
a. Select Deactivate.

244 IBMSystems Director Systems Management Guide

 When setting inventory discovery automation, you can choose to
deactivate or activate (with an associated inventory profile) the
feature.
Activating inventory discovery automation
a. Select Activate - use the following inventory profile.
b. In the Inventory profiles list, select the profile that you
want to use for automatic inventory discovery.
Deactivating inventory discovery automation
a. Select Deactivate.
Common Information Model (CIM) configuration
Configure either unicast, multicast and broadcast, or directory agents
to discover your resources. Also activate or deactivate access request
automation and activate or deactivate inventory discovery automation.

Attention: All three discovery methods (unicast, multicast and

broadcast, and directory agents) are presented on this page and you
can provide information for all three at once. However, only one
method at a time will be used to discover resources. For example, if
you fill in all three sections, only the unicast discovery is performed.
The priority for discovery method processing is as follows:
a. Unicast
b. Directory agents
c. Multicast and broadcast
So, if you want to use multiple methods to discover resources, you
must fill out one section, discover those resources, and then return to
fill out another section and discover those other resources.

Note: You cannot configure directory agents for the following profile
types:
v Hardware management console
v Management controller
v Server, when discovering an IVM
Therefore, ensure that you configure multicast and broadcast if you
choose any of those profile types.
When configuring CIM IP addresses, you can add IP addresses either
individually or as a range, or you can import the addresses.
Adding a single IP address
a. Select Add a single IP address.
b. In the Single IP address or beginning range field, type the
IP address of the resource that you want to discover.
c. Click Add to add the IP address to the list.
d. Repeat this procedure until you have added all the IP
addresses.
Adding a range of IP addresses
a. Select Add a range of IP addresses.
b. For the IP address range that contains the resources that
you want to discover, type the low-end IP address value in
the Single IP address or beginning range field and the
high-end IP address value in the Ending range field.
c. Click Add to add the IP addresses to the list.

Chapter 3. Discovering systems and collecting inventory data 245

 d. Repeat this procedure until you have added all the IP
addresses.
Importing IP addresses
a. Select Import.
b. In the Select the file that you want to import field, type in
the name of the import file or click Browse to search for
the file.

Note: Ensure that the file you use is a line delimited file
with one IP address on each line.
c. Click OK to import the IP addresses.
When configuring multicast and broadcast, select to enable either and
set the timeout period.
Enabling multicast
Select Enable multicast to enable multicast.
Setting the timeout period
In the Timeout period (seconds) field, select the number of
seconds that the server will wait until timing out.
Enabling general broadcast
Select Enable general broadcast to enable general broadcast.
When configuring directory agents, specify either an IP address or a
host name and set the scope.
Adding a directory agent using its IP address
a. Select Add IP address.
b. In the IP address field, type the IP address of the directory
agent that you want to discover.
c. Click Add to add the IP address to the list.
d. Repeat this procedure until you have added all the IP
addresses.
Adding a directory agent using its host name
a. Select Add host name.
b. In the Host name field, type the host name of the directory
agent that you want to discover.
c. Click Add to add the host name to the list.
d. Repeat this procedure until you have added all the host
names.
Setting the scope
Each directory agent is associated with a scope. A discovery
request is targeted to find only those directory agents that are
associated with the specified scope. The directory agent
shipped with IBM Systems Director has a default scope of
DEFAULT, so that is the default scope value used when
searching for directory agents. If you want to search for
directory agents with scopes other than DEFAULT, complete
the following steps:
a. In the Scope field, type the name of a scope that you have
defined.
b. Click Add to add the scope to the list.
c. Repeat this procedure until you have added all the scopes.
When setting access request automation, you can choose to deactivate
or activate (with the appropriate login information) the feature.

246 IBMSystems Director Systems Management Guide

 Activating access request automation
a. Select Activate - use the following user login information.
b. In the User ID field, type a valid user ID for the resource.
c. In the Password field, type the password for the user ID.
Deactivating access request automation
a. Select Deactivate.
When setting inventory discovery automation, you can choose to
deactivate or activate (with an associated inventory profile) the
feature.
Activating inventory discovery automation
a. Select Activate - use the following inventory profile.
b. In the Inventory profiles list, select the profile that you
want to use for automatic inventory discovery.
Deactivating inventory discovery automation
a. Select Deactivate.
Distributed component object model (DCOM) configuration
Configure DCOM IP addresses, activate or deactivate access request
automation, and activate or deactivate inventory discovery
automation.
When configuring DCOM IP addresses, you can add IP addresses
either individually or as a range, or you can import the addresses.
Adding a single IP address
a. Select Add a single IP address.
b. In the Single IP address or beginning range field, type the
IP address of the resource that you want to discover.
c. Click Add to add the IP address to the list.
d. Repeat this procedure until you have added all the IP
addresses.
Adding a range of IP addresses
a. Select Add a range of IP addresses.
b. For the IP address range that contains the resources that
you want to discover, type the low-end IP address value in
the Single IP address or beginning range field and the
high-end IP address value in the Ending range field.
c. Click Add to add the IP addresses to the list.
d. Repeat this procedure until you have added all the IP
addresses.
Importing IP addresses
a. Select Import.
b. In the Select the file that you want to import field, type in
the name of the import file or click Browse to search for
the file.

Note: Ensure that the file you use is a line delimited file
with one IP address on each line.
c. Click OK to import the IP addresses.
When setting access request automation, you can choose to deactivate
or activate (with the appropriate login information) the feature.
Activating access request automation
a. Select Activate - use the following user login information.

Chapter 3. Discovering systems and collecting inventory data 247

 b. In the User ID field, type a valid user ID for the resource.
c. In the Password field, type the password for the user ID.
Deactivating access request automation
a. Select Deactivate.
When setting inventory discovery automation, you can choose to
deactivate or activate (with an associated inventory profile) the
feature.
Activating inventory discovery automation
a. Select Activate - use the following inventory profile.
b. In the Inventory profiles list, select the profile that you
want to use for automatic inventory discovery.
Deactivating inventory discovery automation
a. Select Deactivate.
Interprocess Communication (IPC) configuration
Configure either unicast or multicast and broadcast (general or
directed) to discover your resources and then optionally configure
broadcast relays. Also activate or deactivate access request automation
and activate or deactivate inventory discovery automation.

Note: Access request automation and inventory discovery automation

are not supported on IPC, so these options will not be displayed if
you configure only IPC. However, if you configure IPC along with
other protocols that support access request automation and inventory
discovery automation, those options will be displayed but apply to
only the supported protocols. So, for example, even if you supply the
correct credentials during configuration of access request automation,
you will not gain access to IPC discovered resources when the
automatic access request runs. Instead, you need to request access and
collect inventory manually using the tasks provided by IBM Systems
Director.
When configuring unicast, you can add IP addresses either
individually or as a range, or you can import the addresses.
Adding a single IP address
a. Select Add a single IP address.
b. In the Single IP address or beginning range field, type the
IP address of the resource that you want to discover.
c. Click Add to add the IP address to the list.
d. Repeat this procedure until you have added all the IP
addresses.
Adding a range of IP addresses
a. Select Add a range of IP addresses.
b. For the IP address range that contains the resources that
you want to discover, type the low-end IP address value in
the Single IP address or beginning range field and the
high-end IP address value in the Ending range field.
c. Click Add to add the IP addresses to the list.
d. Repeat this procedure until you have added all the IP
addresses.
Importing IP addresses
a. Select Import.

248 IBMSystems Director Systems Management Guide

 b. In the Select the file that you want to import field, type in
the name of the import file or click Browse to search for
the file.

Note: Ensure that the file you use is a line delimited file
with one IP address on each line.
c. Click OK to import the IP addresses.
When configuring multicast and broadcast, select to enable either,
configure them, and set the timeout period.
Enabling multicast
a. Select Enable multicast.
b. In the Multicast IP address field, enter the IP address that
multicast discovery will use.
Setting the timeout period
In the Timeout period (seconds) field, select the number of
seconds that the server will wait until timing out.
Enabling general broadcast
Select Enable general broadcast to enable general broadcast.
Enabling directed broadcast
a. Select Enable directed broadcast.
b. In the IP address field, enter the IP address that directed
broadcast discovery will use.
c. In the Subnet mask field, enter the subnet mask that
directed broadcast discovery will use.
When configuring the relay broadcast option, specify the agent that
will send the broadcast.
Setting an agent to send a broadcast
a. In the IP address field, enter the IP address of the agent.
b. In the Subnet mask field, enter the subnet mask of the
agent.
c. Click Add to add the host name to the Table of relay data
list.
d. Repeat this procedure until you have added all the agents.
e. If you want to not use a particular agent for broadcasting,
select it in the list and click Delete.
Secure shell (ssh) configuration
Configure ssh IP addresses, activate or deactivate access request
automation, and activate or deactivate inventory discovery
automation.
When configuring ssh IP addresses, you can add IP addresses either
individually or as a range, or you can import the addresses.
Adding a single IP address
a. Select Add a single IP address.
b. In the Single IP address or beginning range field, type the
IP address of the resource that you want to discover.
c. Click Add to add the IP address to the list.
d. Repeat this procedure until you have added all the IP
addresses.

Chapter 3. Discovering systems and collecting inventory data 249

 Adding a range of IP addresses
a. Select Add a range of IP addresses.
b. For the IP address range that contains the resources that
you want to discover, type the low-end IP address value in
the Single IP address or beginning range field and the
high-end IP address value in the Ending range field.
c. Click Add to add the IP addresses to the list.
d. Repeat this procedure until you have added all the IP
addresses.
Importing IP addresses
a. Select Import.
b. In the Select the file that you want to import field, type in
the name of the import file or click Browse to search for
the file.

Note: Ensure that the file you use is a line delimited file
with one IP address on each line.
c. Click OK to import the IP addresses.
When setting access request automation, you can choose to deactivate
or activate (with the appropriate login information) the feature.
Activating access request automation
a. Select Activate - use the following user login information.
b. In the User ID field, type a valid user ID for the resource.
c. In the Password field, type the password for the user ID.
Deactivating access request automation
a. Select Deactivate.
When setting inventory discovery automation, you can choose to
deactivate or activate (with an associated inventory profile) the
feature.
Activating inventory discovery automation
a. Select Activate - use the following inventory profile.
b. In the Inventory profiles list, select the profile that you
want to use for automatic inventory discovery.
Deactivating inventory discovery automation
a. Select Deactivate.
Service Location Protocol (SLP) configuration
Configure either unicast, multicast and broadcast, or directory agents
to discover your resources.

Attention: All three discovery methods (unicast, multicast and

broadcast, and directory agents) are presented on this page and you
can provide information for all three at once. However, only one
method at a time will be used to discover resources. For example, if
you fill in all three sections, only the unicast discovery is performed.
The priority for discovery method processing is as follows:
a. Unicast
b. Directory agents
c. Multicast and broadcast
So, if you want to use multiple methods to discover resources, you
must fill out one section, discover those resources, and then return to
fill out another section and discover those other resources.

250 IBMSystems Director Systems Management Guide

Note: You cannot configure directory agents for the following profile
types:
v Hardware management console
v Management controller
v Server, when discovering an IVM
Therefore, ensure that you configure multicast and broadcast if you
choose any of those profile types.
When configuring unicast, you can add IP addresses either
individually or as a range, or you can import the addresses.
Adding a single IP address
a. Select Add a single IP address.
b. In the Single IP address or beginning range field, type the
IP address of the resource that you want to discover.
c. Click Add to add the IP address to the list.
d. Repeat this procedure until you have added all the IP
addresses.
Adding a range of IP addresses
a. Select Add a range of IP addresses.
b. For the IP address range that contains the resources that
you want to discover, type the low-end IP address value in
the Single IP address or beginning range field and the
high-end IP address value in the Ending range field.
c. Click Add to add the IP addresses to the list.
d. Repeat this procedure until you have added all the IP
addresses.
Importing IP addresses
a. Select Import.
b. In the Select the file that you want to import field, type in
the name of the import file or click Browse to search for
the file.

Note: Ensure that the file you use is a line delimited file
with one IP address on each line.
c. Click OK to import the IP addresses.
When configuring multicast and broadcast, select to enable either and
set the timeout period.
Enabling multicast
Select Enable multicast to enable multicast.
Setting the timeout period
In the Timeout period (seconds) field, select the number of
seconds that the server will wait until timing out.
Enabling general broadcast
Select Enable general broadcast to enable general broadcast.
When configuring directory agents, specify either an IP address or a
host name and set the scope.
Adding a directory agent using its IP address
a. Select Add IP address.
b. In the IP address field, type the IP address of the directory
agent that you want to discover.
c. Click Add to add the IP address to the list.

Chapter 3. Discovering systems and collecting inventory data 251

 d. Repeat this procedure until you have added all the IP
addresses.
Adding a directory agent using its host name
a. Select Add host name.
b. In the Host name field, type the host name of the directory
agent that you want to discover.
c. Click Add to add the host name to the list.
d. Repeat this procedure until you have added all the host
names.
Setting the scope
Each directory agent is associated with a scope. A discovery
request is targeted to find only those directory agents that are
associated with the specified scope. The directory agent
shipped with IBM Systems Director has a default scope of
DEFAULT, so that is the default scope value used when
searching for directory agents. If you want to search for
directory agents with scopes other than DEFAULT, complete
the following steps:
a. In the Scope field, type the name of a scope that you have
defined.
b. Click Add to add the scope to the list.
c. Repeat this procedure until you have added all the scopes.
Simple Network Management Protocol (SNMP) configuration
Configure SNMP IP addresses, optional SNMPv1 or SNMPv2c
community names, and SNMPv3.
When configuring SNMP IP addresses, you can add IP addresses
either individually or as a range, or you can import the addresses.
Adding a single IP address
a. Select Add a single IP address.
b. In the Single IP address or beginning range field, type the
IP address of the resource that you want to discover.
c. Click Add to add the IP address to the list.
d. Repeat this procedure until you have added all the IP
addresses.
Adding a range of IP addresses
a. Select Add a range of IP addresses.
b. For the IP address range that contains the resources that
you want to discover, type the low-end IP address value in
the Single IP address or beginning range field and the
high-end IP address value in the Ending range field.
c. Click Add to add the IP addresses to the list.
d. Repeat this procedure until you have added all the IP
addresses.
Importing IP addresses
a. Select Import.
b. In the Select the file that you want to import field, type in
the name of the import file or click Browse to search for
the file.

Note: Ensure that the file you use is a line delimited file
with one IP address on each line.
c. Click OK to import the IP addresses.

252 IBMSystems Director Systems Management Guide

When configuring SNMPv1/v2c community names, select the protocol
that you want to use and add each community name to the list.
Specifying SNMPv1 or SNMPv2c community names for discovery
a. Select Use SNMPv1 to use the SNMPv1 protocol or
SNMPv2c to use the SNMPv2c protocol.
b. In the Community name field, type the name of a
community name that you have defined.
c. Click Add to add the community name to the list.
d. Repeat this procedure until you have added all the
community names.
When configuring SNMPv3 profiles, you can create new profiles or
edit or delete existing profiles.
Creating a SNMPv3 profile
a. Click Create a profile.
b. In the Profile name field, type a name for the profile.
c. In the User ID field, type a user ID to assign to the profile.
d. In the Authentication protocol field, select an
authentication protocol. Possible values are:
v None (If you select this option, skip to the Context
engine name (optional) field.)
v MD5
v SHA
e. In the Authentication password field, set a password for
authentication.
f. In the Confirm authentication password field, retype the
authentication password.
g. In the Privacy protocol field, select a privacy protocol.
Possible values are:
v None (If you select this option, skip to the Context
engine name (optional) field.)
v AES
v DES
h. In the Privacy password field, set a password for privacy.
i. In the Confirm privacy password field, retype the privacy
password.
j. In the Context engine name (optional) field, type the name
of any context engine that you want to specify.
k. In the Context engine ID (optional) field, type the ID of
the context engine.
l. Click Apply to add the profile to the SNMPv3 profiles list.
Deleting a SNMPv3 profile
a. In the SNMPv3 profiles list, select the profile that you
want to delete.
b. Click Delete a profile.
Editing a SNMPv3 profile
a. In the SNMPv3 profiles list, select the profile that you
want to edit.

Chapter 3. Discovering systems and collecting inventory data 253

 b. Click Edit a profile.
c. Modify entries in the fields as needed.
d. Click Apply.
Storage Management Initiative Specification (SMI-S) configuration
Configure either a direct connection, multicast and broadcast, or a
proxy using directory agents. Also activate or deactivate access request
automation and activate or deactivate inventory discovery automation.

Note: You cannot configure directory agents for the following profile
types:
v Hardware management console
v Management controller
v Server, when discovering an IVM
Therefore, ensure that you configure multicast and broadcast if you
choose any of those profile types.
Select a discovery type at the top of the page to display options for
configuring that type.
When configuring a direct connection, you select a hardware type,
protocol, IP address, and port.
Configuring a direct connection
a. In the Hardware type field, select the type of hardware of
the resource to which you want to connect. Choose from
the following types:
v IBM System Storage DS3000/DS4000
v IBM System Storage DS6000
v QLogic fibre channel switch
v Brocade fibre channel switch
v IBM BladeCenter S SAS RAID Controller Module
b. In the Protocol field, select the protocol to use to make the
connection. Choose from the following protocols:
v https
v http
c. In the IP address field, specify the IPv4 IP address of the
resource.
d. In the Port field, specify the port on which the resource
listens.
When configuring multicast and broadcast, select to enable either and
set the timeout period.
Enabling multicast
Select Enable multicast to enable multicast.
Setting the timeout period
In the Timeout period (seconds) field, select the number of
seconds that the server will wait until timing out.
Enabling general broadcast
Select Enable general broadcast to enable general broadcast.
When configuring a proxy using directory agents, specify either an IP
address or a host name and set the scope.

254 IBMSystems Director Systems Management Guide

 Adding a directory agent using its IP address or host name
a. In the IP address or host name field, type the IP address
or host name of the directory agent that you want to
discover.
b. Click Add to add the IP address or host name to the list.
c. Repeat this procedure until you have added all the IP
addresses or host names.
Setting the scope
Each directory agent is associated with a scope. A discovery
request is targeted to find only those directory agents that are
associated with the specified scope. The directory agent
shipped with IBM Systems Director has a default scope of
DEFAULT, so that is the default scope value used when
searching for directory agents. If you want to search for
directory agents with scopes other than DEFAULT, complete
the following steps:
a. In the Scope field, type the name of a scope that you have
defined.
b. Click Add to add the scope to the list.
c. Repeat this procedure until you have added all the scopes.
When setting access request automation, you can choose to deactivate
or activate (with the appropriate login information) the feature.
Activating access request automation
a. Select Activate - use the following user login information.
b. In the User ID field, type a valid user ID for the resource.
c. In the Password field, type the password for the user ID.
Deactivating access request automation
a. Select Deactivate.
When setting inventory discovery automation, you can choose to
deactivate or activate (with an associated inventory profile) the
feature.
Activating inventory discovery automation
a. Select Activate - use the following inventory profile.
b. In the Inventory profiles list, select the profile that you
want to use for automatic inventory discovery.
Deactivating inventory discovery automation
a. Select Deactivate.
12. Click Next. The Summary page is displayed.
13. Click Finish.

When you are finished creating the profile, it will appear in the table on the
Advanced System Discovery page. You can then select the profile to run other
management tasks, such as copying it or editing it, or run the profile.

Chapter 3. Discovering systems and collecting inventory data 255

 Related concepts
“Discovery” on page 231
“Manageable systems” on page 7
“Discovery protocols” on page 232
“System discovery” on page 237
“Discovery profiles” on page 239
Related tasks
“Managing access” on page 713
“Managing discovery profiles”
“Performing an advanced system discovery” on page 48
“Collecting and viewing inventory data” on page 259
“Discovering and collecting inventory for storage devices” on page 590

Managing discovery profiles

From the Advanced System Discovery page, you can copy, edit, or delete a
discovery profile.

To copy, edit, or delete a discovery profile, the profile must already exist. You can
also use this page to create a new discovery profile that you can then manage. See
“Creating a discovery profile” for instructions.

To copy, edit, or delete a discovery profile, complete the following steps:

1. Open the Advanced System Discovery page using either of these two methods:
v On the Welcome page, click Advanced System Discovery under Optional
tasks.
v In the IBM Systems Director Web interface navigation area, expand
Inventory and then click Advanced System Discovery.
2. On the Advanced System Discovery 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 19. Discovery profile actions
To do this task: Complete these steps:
Copy an existing discovery profile 1. Select the profile that you want to copy.
2. Click Create like. The Advanced System
Discovery 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.
3. Edit the profile properties as needed,
clicking Next to continue through the
wizard.
4. Click Finish. The new profile based on
the original profile will appear in the
table on the Advanced System Discovery
page.

256 IBMSystems Director Systems Management Guide

 Table 19. Discovery profile actions (continued)
To do this task:
Edit an existing discovery profile
Delete an existing discovery profile
Complete these steps:
1. Select the profile that you want to edit.
2. Click Edit. The Advanced System
Discovery wizard is displayed.
3. Edit the profile properties as needed,
clicking Next to continue through the
wizard.
4. Click Finish.
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. The selected profile is deleted and is
no longer displayed in the table on the
Advanced System Discovery 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
“Discovery profiles” on page 239
“Discovery” on page 231
“Discovery protocols” on page 232
“System discovery” on page 237
Related tasks
“Creating a discovery profile” on page 34
“Performing an advanced system discovery” on page 48

Performing an advanced system discovery

Use advanced system discovery to identify and manage a specific type of resource.
Advanced system discovery is helpful when you want to limit your discovery
using criteria that you specify.

Before performing an advanced system discovery, ensure that the discovery profile
that you want to use exists. If the profile that you want to use does not exist, you
must reconfigure an existing profile for your use or create a new one.

During advanced system discovery, IBM Systems Director Server attempts to

contact only the resource types that you specify by using the specific protocols
defined in the discovery profile. If IBM Systems Director Server successfully
contacts the resource, it is displayed in the appropriate groups in Navigate
Resources.

To perform an advanced system discovery, complete the following steps:

1. Open the Advanced System Discovery page using either of these two methods:
v On the Welcome page, click Advanced System Discovery under Optional
tasks.
v In the IBM Systems Director Web interface navigation area, expand
Inventory and then click Advanced System Discovery.

Chapter 3. Discovering systems and collecting inventory data 257

 2. On the Advanced System Discovery page, select one or more discovery profiles
that you want to use for discovery.

Note: If the discovery profile that you want to use for the advanced system
discovery does not already exist, click Create to start the Advanced Discovery
Wizard.
3. Click Run. The Run - Advanced Systems Discovery page is displayed.
4. Use the Run - Advanced Systems Discovery page to set up optional functions
and options of your system discovery task:
Schedule
Use the Schedule page to set the discovery 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 page to choose options for an email notification
that you can receive as the discovery process progresses.
Options
Use the Options page to specify the time to use for the system time and
how to handle unavailable systems.
5. When you are finished with the Run - Advanced Systems Discovery page, click
OK. A discovery job is created and a message is displayed with buttons and
information 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 discovery is completed, the discovered systems are displayed in Navigate

Resources.

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.

258 IBMSystems Director Systems Management Guide

 Related concepts
“Discovery profiles” on page 239
“Discovery” on page 231
“Discovery protocols” on page 232
“System discovery” on page 237
“Inventory data and collection profiles”
Related tasks
“Creating a discovery profile” on page 34
“Managing discovery profiles” on page 256
“Accessing a secured system with request access” on page 714
“Discovering and collecting inventory for storage devices” on page 590
“Viewing active and scheduled job information” on page 205
“Finding and navigating resources” on page 95
“Managing inventory collection profiles” on page 262
“Collecting inventory” on page 68

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 using System Discovery or Advanced System Discovery
and also have access to it.
Related concepts
“Discovery” on page 231
“Discovery protocols” on page 232
“System discovery” on page 237
“Discovery profiles” on page 239
Related tasks
“Creating a discovery profile” on page 34
“Discovering systems with system discovery” on page 237
“Discovering systems with advanced system discovery” on page 239
“Accessing a secured system with request access” on page 714

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 View Inventory 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.

Chapter 3. Discovering systems and collecting inventory data 259

 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.
Basic System Information
This profile collects inventory from system resources.
All Hardware Inventory
This profile collects inventory from physical and virtual devices.
All Software Inventory
This profile collects inventory from software resources.
Software Images Discovery
This profile collects inventory from software images.

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.

260 IBMSystems Director Systems Management Guide

 Related concepts
“Update manager” on page 12

Creating an inventory collection profile

Use the Create Inventory Profile wizard to create an inventory collection profile.

If you do not want to use one of the profiles that is 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, complete the following steps:

1. Open the View and Collect Inventory page using either of these two methods:
v On the Welcome page, click Collect and view inventory under Optional
tasks.
v In the IBM Systems Director Web interface navigation area, expand
Inventory and then click View and 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. The Discovery Service page is displayed.
11. Select the option that reflects your decision about whether you want to
configure the discovery services or let the system choose the services for you.
12. Click Next. If you selected Let me manually configure the discovery services,
the Module Selection page is displayed.

Note: If you selected Let the system choose the discovery services, skip right
to the steps about the Options page.
13. Select the discovery modules that you want to configure to discover
additional attributes on your resources.
14. Click Next. Pages for each of the discovery modules that you selected are
displayed.
15. Complete the pages for each discovery module.
16. Click Next. The Options page is displayed.
17. 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

Chapter 3. Discovering systems and collecting inventory data 261

 value elapses before the response is received from the destination no
inventory data will be collected from that target.
18. 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.
19. To instruct IBM Systems Director Server to automatically retry failed collection
attempts, select Retry failed agents.
20. Click Next. The Summary page is displayed.
21. Click Finish.

After creating an inventory collection profile, you can run it by clicking Collect
Inventory.
Related concepts
“Inventory data and collection profiles” on page 259
Related tasks
“Collecting inventory” on page 68
“Managing inventory collection profiles”
“Viewing inventory” on page 69

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:
1. Open the View and Collect Inventory page using either of these two methods:
v On the Welcome page, click Collect and view inventory under Optional
tasks.
v In the IBM Systems Director Web interface navigation area, expand
Inventory and then click View and 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. 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.

262 IBMSystems Director Systems Management Guide

 Table 20. Inventory collection profile actions
To do this task: Complete these steps:
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.
3. Edit the profile properties as needed,
clicking Next to continue through the
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.
3. Edit the profile properties as needed,
clicking Next to continue through the
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
“Inventory data and collection profiles” on page 259
Related tasks
“Creating an inventory collection profile” on page 261
“Performing an advanced system discovery” on page 48

Collecting inventory
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 or Advanced 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.

Chapter 3. Discovering systems and collecting inventory data 263

 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 → Request Access.

To collect inventory for one or more systems, complete the following steps:
1. Open the View and Collect Inventory page using either of these two methods:
v On the Welcome page, click Collect and view inventory under Optional
tasks.
v In the IBM Systems Director Web interface navigation area, expand
Inventory and then click View and Collect Inventory.
The View and Collect Inventory page is displayed.
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, complete 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 Manage inventory profiles 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 choose 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 a message is displayed with buttons and
information 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 View Inventory.

264 IBMSystems Director Systems Management Guide

 Related concepts
“Discovery” on page 231
“Manageable systems” on page 7
“Inventory data and collection profiles” on page 259
Related tasks
“Creating an inventory collection profile” on page 261
“Viewing inventory” on page 69
“Performing a system discovery” on page 32
“Performing an advanced system discovery” on page 48
“Viewing active and scheduled job information” on page 205

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 → Request Access.

To display inventory data for a resource, complete the following steps:

1. Open the View and Collect Inventory page using either of these two methods:
v On the Welcome page, click Collect and view inventory under Optional
tasks.
v In the IBM Systems Director Web interface navigation area, expand
Inventory and then click View and Collect Inventory.
The View and Collect Inventory page is displayed.
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, complete 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 Manage inventory profiles list, select the inventory profile that you
want to use.

Chapter 3. Discovering systems and collecting inventory data 265

 4. Click View Inventory. The inventory data for the selected resource is
displayed.

Note: If you click View Inventory 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
“Inventory data and collection profiles” on page 259
Related tasks
“Collecting inventory” on page 68
“Creating an inventory collection profile” on page 261

266 IBMSystems Director Systems Management Guide

Chapter 4. Configuring systems
Using IBM Systems Director configuration manager, you can configure both
hardware devices and systems so that they will work together and meet the needs
of your environment.

You must understand the following terms to effectively configure systems using
IBM Systems Director.
Configuration setting
Real-time values associated with a particular aspect of a system or device,
such as login information or SNMP options, which can be saved as a
configuration template or as a configuration plan.
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.
Related tasks
“Configuring templates” on page 508

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.

Configuration templates
A configuration template is a stored version of device parameters and settings,
which can be reused or deployed at a later time.

You can create, view, edit, delete, deploy, and schedule configuration templates to
be deployed on a target resource.

© Copyright IBM Corp. 1999, 2009 267

 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:

chassis/bc1
IBM BladeCenter chassis
chassis/bc2
IBM BladeCenter H chassis
chassis/telco
IBM BladeCenter T chassis
chassis/telco2
IBM BladeCenter HT chassis
chassis/bcs1
IBM BladeCenter S chassis
I/O Module Ethernet Switch
The Ethernet switch attached to an IBM BladeCenter I/O module
I/O Module Fibre Switch
The Fibre channel switch attached to an IBM BladeCenter I/O module
I/O Module InfiniBand Switch
The InfiniBand switch attached to an IBM BladeCenter I/O module
I/O Module Storage Switch
The Storage switch attached to an IBM BladeCenter I/O module
Server/IBM:SVR:Chassis:Stand-aloneServer
Stand-alone server

Tips:
v When you make changes to 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.
Note that you can delete a configuration template that is in one or more
configuration plan, but you will receive 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 be defined first.
If an inappropriate order is chosen, errors might be issued when the
configuration plan is deployed. When deploying a configuration plan, check the
status to determine whether it succeeded and analyze any errors received.

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.

268 IBMSystems Director Systems Management Guide

 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.

A configuration plan can be set up so that it is 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.

Types

A type is the category of resource that a configuration template is to define. These

are the types for a configuration template. 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

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.

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.

Chapter 4. Configuring systems 269

 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 (click Automation → Event Filters).

Note: This task requires the IBM Systems Director Launched Tasks program. This
program is installed automatically the first time you use a task that requires it. For
information about the IBM Systems Director Launched Tasks program, see
“Starting the IBM Systems Director Launched Tasks program.”

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.

270 IBMSystems Director Systems Management Guide

 3. In the Event Automation Plan wizard, the Welcome page is displayed. 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 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.
8. In the Create Filter window, select the simple filter type and click OK. The
IBM Systems Director Web interface starts the IBM Systems Director Launched
Tasks program. This program subsequently displays the Event Filter Builder
window.
9. In the Event Filter Builder window, clear the Any check box on the Event
Type page.
10. Expand the Event Type tree to view the configuration manager events by
clicking IBM Systems Director Program → System Configuration.
11. Select the applicable configuration manager event:

Option Description
To monitor for the deployment of Expand Configuration Template and select
configuration templates Deployed
To monitor for the deployment of Expand Configuration Plan and select
configuration plans Deployed

12. Click File → Save As.

13. In the Save Event Filter window, type a name for the filter.
14. Click OK to save the filter. The new filter is displayed on the Advanced Event
Filters page.
15. When you are satisfied with the event filter, click Next.
16. On the Events actions page, click Create.
17. In the Create Actions window, select an event action, for example, Send an
e-mail (Internet SMTP)
18. Click OK.
19. 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.”
20. When you are satisfied with the settings, click File → Save As. In the Save
Event Action window, type a name for the action.
21. When you are satisfied with your selected event actions, click Next.
22. On the Time range page, choose the period of time over which you want to
collect the events. Select All day (24 x 7) to enable the plan to be active all the
time.
23. When you are satisfied with the specified time ranges, click Next.
24. On the Summary page, verify the details of the event automation plan. If you
need to make changes, click < Back.
25. When you are done editing the event automation plan, click Finish.

Chapter 4. Configuring systems 271

 The event automation plan is saved and is displayed in the Event Automation
Plans page.

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.

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 Navigate Resources 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 a: 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

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 Navigate Resources 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 a: 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.
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 OK. The changes are applied, and you are returned to the list of
configuration settings for the system.
8. Click Close.

272 IBMSystems Director Systems Management Guide

 As an alternative, you can start this task from the navigator area by selecting
System Configuration → Current Configuration

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 Navigate Resources section, 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 a: 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.
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.

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.

Chapter 4. Configuring systems 273

 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.

Managing configuration templates

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

Creating configuration templates

Create a configuration template to hold definitions for a specific resource.

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 (%)

274 IBMSystems Director Systems Management Guide

 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:
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 (<)
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 occur, click
Automatically deploy. To determine which configuration settings supports the
Automatically deploy option, display the Configuration Manager Summary
page and select Configuration Settings, the Configuration Settings list will
show which configuration settings support Automatically deploy for the
configuration template.
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.

Creating a configuration template from an existing one

You can create a configuration template using an existing configuration template as
a model.

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 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 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 (?)

Chapter 4. Configuring systems 275

 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:
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 (<)
6. Optional: If you want this configuration template to run automatically when a
new device with a type that matches this configuration template is added, click
Automatically deploy.
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.

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.

Note: For more information about navigating and working with tables in IBM
Systems Director Web interface, see “Table navigation in IBM Systems Director.”

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.

Editing configuration templates

Some attributes of a configuration template can be changed after it is created.

Using the edit function, you can change the resources that the configuration
template defines.

Note: For more information about navigating and working with tables in IBM
Systems Director Web interface, see “Table navigation in IBM Systems Director.”

You cannot change the target type of the configuration template and automatic
deployment status. You can change the resources that the configuration template
defines with the Edit function.

To edit 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 a configuration template to edit.

276 IBMSystems Director Systems Management Guide

 3. Click Actions → Edit Template. The Configuration Template page is displayed.
4. Make all necessary changes.
5. Click Save. The changes will be applied to the configuration template.

Using the Properties function, you can change other attributes of the configuration
template such as the name, description, and configuration plan membership.

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.

Note: For more information about navigating and working with tables in IBM
Systems Director Web interface, see “Table navigation in IBM Systems Director.”

To add a configuration template to a configuration plan, complete the following

steps:
1. From the Configuration manager summary page, click View Configuration
Templates. The Configuration Templates page is displayed.
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 type a unique name and
description to create a new configuration plan. Choose the value for the
automatic deployment setting also.
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.

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:
1. From the Configuration manager summary page, click View Configuration
Templates. The Configuration Templates page is displayed.
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.

Chapter 4. Configuring systems 277

 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.

Viewing deployed targets

You can view the devices and systems on which a configuration template has been
deployed, to determine where changes are required.

Note: For more information about navigating and working with tables in IBM
Systems Director Web interface, see “Table navigation in IBM Systems Director.”

To view the list of devices and systems on which a configuration template has
been deployed on, complete the following steps:
1. From the Configuration manager summary page, click View Configuration
Templates. The Configuration Templates page is displayed.
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.

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.

Note: For more information about navigating and working with tables in IBM
Systems Director Web interface, see “Table navigation in IBM Systems Director.”

To export a configuration template, complete the following steps:

1. From the Configuration manager summary page, click View Configuration
Templates. The Configuration templates page is displayed.

278 IBMSystems Director Systems Management Guide

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

Importing a configuration template

An XML file containing a configuration template can be imported to your list of
configuration templates.

Note: For more information about navigating and working with tables in IBM
Systems Director Web interface, see “Table navigation in IBM Systems Director.”

To import an XML file containing 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. 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.

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.

Note: For more information about navigating and working with tables in IBM
Systems Director Web interface, see “Table navigation in IBM Systems Director.”

To delete 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 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.

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.

Chapter 4. Configuring systems 279

 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.

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 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.
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
configuration templates.
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.

280 IBMSystems Director Systems Management Guide

 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.

Creating a configuration plan from an existing one

An existing configuration plan can be used as a model for creating a new one.

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 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.

Deploying configuration plans

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.

Note: For more information about navigating and working with tables in IBM
Systems Director Web interface, see “Table navigation in IBM Systems Director.”

To deploy a configuration plan on a target system, complete the following steps:

1. From the Configuration manager summary page, click View Configuration
Plans. The Configuration plans page is displayed.
2. Select the configuration plan.

Chapter 4. Configuring systems 281

 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.

Viewing configuration plans

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.

Note: For more information about navigating and working with tables in IBM
Systems Director Web interface, see “Table navigation in IBM Systems Director.”

To view a configuration plan, complete the following steps:

1. From the Configuration manager summary page, click View Configuration
Plans. The Configuration plans page is displayed.
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.

Viewing deployment history

Use this procedure to view the deployment history for a system. A table listing the
attempts to deploy both configuration plans and configuration template is
displayed.

Note: For more information about navigating and working with tables in IBM
Systems Director Web interface, see “Table navigation in IBM Systems Director.”

282 IBMSystems Director Systems Management Guide

 To view a system’s configuration history, complete the following steps:
1. From the Navigate Resources 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.

Editing configuration plans

The attributes of a configuration plan can be changed after it is created.

Note: For more information about navigating and working with tables in IBM
Systems Director Web interface, see “Table navigation in IBM Systems Director.”

To edit a configuration plan, complete the following steps:

1. From the Configuration manager summary page, click View Configuration
Plans. The Configuration plans page is displayed.
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.

Exporting a configuration plan

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.

Note: For more information about navigating and working with tables in IBM
Systems Director Web interface, see “Table navigation in IBM Systems Director.”

To export a configuration plan, complete the following steps:

1. From the Configuration manager summary page, click View Configuration
Plans. The Configuration plans page is displayed.
2. Select the configuration plan that you want to export. Only one configuration
plan can be exported to any given file.
3. Click Actions → Export.
4. Type the name of the file to receive the exported data.
5. Click Save.

Chapter 4. Configuring systems 283

 Importing a configuration plan
An XML file containing a configuration plan can be imported to your list of
configuration plans.

Note: For more information about navigating and working with tables in IBM
Systems Director Web interface, see “Table navigation in IBM Systems Director.”

To import and XML file containing a configuration plan, complete the following
steps:
1. From the Configuration manager summary page, click View Configuration
Plans. The Configuration plans page is displayed.
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.

Deleting configuration plans

You can delete those configuration plans that are no longer needed, in order to
save space and prevent them from being used.

Note: For more information about navigating and working with tables in IBM
Systems Director Web interface, see “Table navigation in IBM Systems Director.”

Complete the following steps to delete a configuration plan:

1. From the Configuration manager summary page, click View Configuration
Plans. The Configuration plans page is displayed.
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.

284 IBMSystems Director Systems Management Guide

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
Chapter 6, “Automating tasks,” on page 333
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.

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.

IBM Systems Director provides several tools and views to monitor and manage the
resources within your environment. Use the following System Status and Health
tasks to view the system’s status:
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 you need to create monitors for
resources in your environment. Use these monitors to retrieve the real-time
status and quantitative data for specific properties and attributes of the
resources. You can also set thresholds for the monitors, graph the data that
they 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. Note that 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

© Copyright IBM Corp. 1999, 2009 285

 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
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.
Event Log
An event is an occurrence of significance to a task or resource. Examples of
events include the completion of an operation, the failure of a hardware
component, or the exceedance of a processor threshold. The Event Log task
displays all events that are received from any number of sources by IBM
Systems Director Server.
SNMP Management
The SNMP Management task provides two tasks for the management of
SNMP. With the SNMP browser, you can select the targets on which a
SNMP job will run. With the MIB Management window, you can compile
or load MIBs.

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.

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.

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 Navigate Resources page and navigate
directly to the new hardware to view its status.

286 IBMSystems Director Systems Management Guide

 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.

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. Note that information on the summary page is
refreshed automatically when there are any changes.

To view the status manager summary, complete the following steps:

1. In the IBM Systems Director navigation area, click Welcome.
2. On the Welcome page, click the Manage tab. A list of available summary pages
is displayed.
3. On the Manage tab, scroll to the Status manager section heading and click it.
The status manager summary is displayed.
4. 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

Click any of the category list items to see a breakdown of the systems in that
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.
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.
5. View the Management section. This section provides the following information:

Chapter 5. Monitoring system status and health 287

 v The number of recordings that are active and completed. Click the link to
view the Recordings page
v The number of thresholds that are active and not active. Click the link to
view the Thresholds page
v In the Common tasks area, the following links are provided:
Monitors
Use the Monitors page to create and work with monitors.
Thresholds
Use the Thresholds page to work with thresholds.
Recordings
Use the Recordings page to create and work with recordings.
Event log
Use the Event Log page to view events according to filters that you
select.
6. View the Details section. This section provides the following information:
v Detailed status by category.

Using the Health Summary task to view the status of your environment
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.

Before you can view the status of any resources, IBM Systems Director must first
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:

288 IBMSystems Director Systems Management Guide

 1. In the IBM Systems Director Web interface navigation area, expand System
Status and Health and click Health Summary. The Health Summary page,
including the scoreboard, dashboard, and health summary sections, displays
the status and health of your environment.
2. Choose an item and drill down to view its details.
Related tasks
“Finding systems and other resources” on page 61
“Managing groups” on page 146

Scoreboard
The Scoreboard section of the Health Summary page makes it easy to monitor the
health of systems in your environment. IBM Systems Director Server automatically
monitors the vital signs related to the health and performance of systems that have
been discovered. When the status of a system reaches a critical, warning, or
informational level, the system is counted and added to the totals in the
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. Before you
can view the status of any resources, IBM Systems Director must first discover and
be able to access those resources.

The scoreboard displays the status of important areas of your environment 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:

Chapter 5. Monitoring system status and health 289

 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.

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 a variety of 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.

290 IBMSystems Director Systems Management Guide

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:

1. In the IBM Systems Director Web interface navigation area, expand System
Status and Health and click Health Summary. The scoreboard, dashboard, and
health summary display the status and health of your environment.

Chapter 5. Monitoring system status and health 291

 2. In the scoreboard, select one of the following filtering methods:
Table 21. Filtering methods
To do this task:
Filter based on severity status
Filter based on type of issue
Filter based on both status and issue
292 IBMSystems Director Systems Management Guide
Complete these steps:
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 Navigate
Resources table.
In the scoreboard, click one of the listed
categories. The resources with the selected
issue type are displayed in the Navigate
Resources table.
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.
 3. 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.
4. Click through the pages until you find the resource that has caused the
problem.
Related concepts
“System severity states” on page 88

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:
1. In the IBM Systems Director Web interface navigation area, expand System
Status and Health and click Health Summary.
2. In the dashboard, click Show Monitors. The Monitors page is displayed.
3. To select one or more target resources, click Browse. The Context Chooser is
displayed.
4. 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.
5. From the Monitor selection page, select the monitor view that you want to be
displayed for the targets that you selected.
6. Click Show Monitors. The Monitor View page listing monitors for the targets
that you selected is displayed.
7. 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:

1. In the IBM Systems Director Web interface navigation area, expand System
Status and Health and click Health Summary.

Chapter 5. Monitoring system status and health 293

 2. 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 Navigate Resources 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:
1. In the IBM Systems Director Web interface navigation area, expand System
Status and Health and click Health Summary. The scoreboard, dashboard,
and health summary display the status and health of your environment.
2. In the health summary, right-click Favorites and select Edit. The Group Editor
Wizard opens and the Welcome page is displayed.
3. Click Next. The Name page is displayed and the Name and Description fields
are filled out for your favorites group.
4. 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.
5. Click Next. The Define page is displayed.
6. To add systems to the group, select the systems or criteria in the list on the
left and click Add.
7. To remove systems from the group, select the systems or criteria in the list on
the right and click Remove.
8. Continue modifying resources or criteria as needed.
9. Click Next. The Summary page is displayed.
10. 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.

294 IBMSystems Director Systems Management Guide

To add a group to the health summary using the Actions menu on the health
summary, complete the following steps:
1. In the IBM Systems Director Web interface navigation area, expand System
Status and Health and click Health Summary. The scoreboard, dashboard,
and health summary display the status and health of your environment.
2. In the health summary, click Actions → Edit. The Group Editor wizard opens.
3. In the Name field, type a descriptive name of the health summary group that
you want to create.
4. In the Description field, type a brief description for the group.
5. Click Next. The Type page is displayed.
6. 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 will prompt you to specify the criteria that the system
attributes and properties must match. Then, when a system’s
attributes or properties change, its match to the group criteria changes
and IBM Systems Director automatically adds or removes the system
to or from the group.
7. In the Member list, select the type of members to add to the group.
8. Click Next.
9. In the left area, select the resources or criteria to use for the group, and click
Add.
10. Continue adding resources or criteria as needed.
11. 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 Navigate Resources to add systems to the health

summary
Use the Navigate Resources 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 using the Navigate Resources task,
complete the following steps:
1. In the IBM Systems Director Web interface navigation area, click Navigate
Resources.
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 Navigate Resources 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.
Chapter 5. Monitoring system status and health 295
 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:
1. In the IBM Systems Director Web interface navigation area, expand System
Status and Health and click Health Summary. The scoreboard, dashboard, and
health summary display the status and health of your environment.
2. In the health summary, right-click the group that you want to remove and click
Remove. A confirmation message is displayed.
3. Click Remove. The group is removed.

Using Navigate Resources to view the status of a specific resource

Use Navigate Resources when you want to view the status of only one resource
and you know exactly which resource it is. Using the Navigate Resources task, you
can navigate to a specific resource and drill down to view detailed status
information.

Before you can view the status of any resources, IBM Systems Director must first
discover and be able to access those resources.

To view the status of a specific resource using the Navigate Resources task,
complete the following steps:
1. In the IBM Systems Director Web interface navigation pane, click Navigate
Resources.

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
“Finding systems and other resources” on page 61
“Managing groups” on page 146

Managing monitors
The Monitors task provides the tools you need to create monitors for resources in
your environment. Use these monitors to retrieve the real-time status and
quantitative data for specific properties and attributes of the resources. You can
also set thresholds for the monitors, graph the data that they 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.

296 IBMSystems Director Systems Management Guide

 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

Resource-monitor attributes
You can use the Resource Monitors task to monitor critical system resources on
managed systems. The resources that you can monitor are different depending on
the operating system that is installed on the managed system. Use these
resource-monitor attributes tables to identify the resource-monitor attributes that
you want to monitor if you are planning your IBM Systems Director installation or
configuration or adjusting your resource-monitoring strategy.

Commonly-used sets of monitors are available for use. For more information, see
“Creating a monitor view.” Using monitor views, you also can select specific
monitors that are not provided in the commonly-used sets.

Resource monitor data-collection intervals vary depending on the managed system

or device. In general, using the default settings, data collections occur every 5 to 10
seconds, and the display refreshes every 10 to 20 seconds. These intervals will
affect the minimum granularity and timeliness of any thresholds applied to the
resource-monitor attributes.

AIX resource-monitor attributes

These resource-monitor attributes are for the AIX operating system.

Resource
monitor Attributes
CPU v CPU utilization
Note: CPU utilization for Common-Agent managed systems running AIX
is calculated in the following ways:
For AIX 5.2 and AIX 5.3 LPARs in dedicated or shared and capped
mode CPU utilization is calculated based on the user, sys, wait and idle
values returned by the lparstat command.
For AIX 5.3 LPARs in shared and uncapped mode:
CPU utilization is the entitlement percentage returned by the
lparstat command.
v Process count
Disk Notes:
1. The disk drive monitor attributes are repeated for each local
nonremovable logical drive that is found.
2. The list of file-system attributes is displayed first; then, the disk monitor
attributes are displayed under each file system.
v Blocks available
v Blocks used
v Inodes available
v Inodes used
v Percentage blocks available
v Percentage block used
v Percentage Inodes available
v Percentage Inodes used
v Percentage space available
v Percentage space used
v Space available (MB)
v Space used (MB)

Chapter 5. Monitoring system status and health 297

 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.
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
Memory v Available (bytes)
v Used (bytes)
v Total memory
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 Yesterday’s execution time
v Yesterday’s new executions
UNIX v CPU monitors
system v Disk monitors
v Memory monitors
CIM Note: The attributes for CIM monitors can vary depending on the features
and functions that you have configured on the managed system.
v CIMV2
v ibmsd
v ibmsd_remote
v pg_internal
v pg_interop

IBM i resource-monitor attributes

These resource-monitor attributes are for the IBM i operating system.

298 IBMSystems Director Systems Management Guide

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 additional 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
may 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
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

Chapter 5. Monitoring system status and health 299

 Resource
monitor Attributes
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 Yesterday’s execution time
v Yesterday’s new executions
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
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

300 IBMSystems Director Systems Management Guide

Resource
monitor Attributes
™
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 %
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

Linux resource-monitor attributes

These resource-monitor attributes are for the Linux on System x and Linux on
System z operating systems.

Chapter 5. Monitoring system status and health 301

 Resource
monitor Attributes
CPU v CPU utilization
v Process count
Disk Notes:
1. The disk drive monitor attributes are repeated for each local
nonremovable logical drive that is found.
2. The list of file-system attributes is displayed first; then, the disk monitor
attributes are displayed under each file system.
v Blocks available
v Blocks used
v Inodes available
v Inodes used
v Percentage blocks available
v Percentage block used
v Percentage Inodes available
v Percentage Inodes used
v Percentage space available
v Percentage space used
v Space available (MB)
v Space used (MB)
v Volume SYS: space remaining
v Volume SYS: space used
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 additional 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.
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

302 IBMSystems Director Systems Management Guide

Resource
monitor Attributes
File system Note: The file system monitor attributes for specific directories are provided
for typical Linux 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 /lost+found
v /sbin
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
Memory v Available (bytes)
v Used (bytes)
v Total memory
v Unused non-cached (MBytes)
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 Yesterday’s execution time
v Yesterday’s new executions
UNIX v CPU monitors
system v Disk monitors
v Disk performance monitors
v Memory monitors
v Network monitors
CIM Note: The attributes for CIM monitors can vary depending on the features
and functions that you have configured on the managed system.
v Namespaces
v Classes
v Instances
v Properties

Chapter 5. Monitoring system status and health 303

 Linux on Power Systems resource-monitor attributes
These resource-monitor attributes are for the Red Hat Enterprise Linux AS for
Linux on Power Systems and SUSE Linux Enterprise Server 9 on IBM Power
Systems operating systems.

Resource
monitor Attributes
CPU v CPU utilization
v Process count
Disk Notes:
1. The disk drive monitor attributes are repeated for each local
nonremovable logical drive that is found.
2. The list of file-system attributes is displayed first; then, the disk monitor
attributes are displayed under each file system.
v Blocks available
v Blocks used
v Inodes available
v Inodes used
v Percentage blocks available
v Percentage block used
v Percentage Inodes available
v Percentage Inodes used
v Percentage space available
v Percentage space used
v Space available (MB)
v Space used (MB)
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 additional 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.
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
List of v Directory attributes
directory v Directory exists
contents v Directory owner
v Directory size (bytes)
v Last modified
v Object type

304 IBMSystems Director Systems Management Guide

Resource
monitor Attributes
Memory v Available (bytes)
v Used (bytes)
v Total memory
v Unused non-cached (MBytes)
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 Yesterday’s execution time
v Yesterday’s new executions
CIM Note: The attributes for CIM monitors can vary depending on the features
and functions that you have configured on the managed system.
v CIMV2
v ibmsd
v ibmsd_remote
v pg_internal
v pg_interop

UNIX resource-monitor attributes

These resource-monitor attributes are for the UNIX operating system.

Resource
monitor Attributes
CPU v CPU utilization
v Process count

Chapter 5. Monitoring system status and health 305

 Resource
monitor Attributes
Disk Notes:
1. The disk drive monitor attributes are repeated for each local
nonremovable logical drive that is found.
2. The list of file-system attributes is displayed first; then, the disk monitor
attributes are displayed under each file system.
v Blocks available
v Blocks used
v Inodes available
v Inodes used
v Percentage blocks available
v Percentage block used
v Percentage Inodes available
v Percentage Inodes used
v Percentage space available
v Percentage space used
v Space available (MB)
v Space used (MB)
v Volume SYS: space remaining
v Volume SYS: space used
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 additional 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.
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

306 IBMSystems Director Systems Management Guide

Resource
monitor Attributes
File system Note: The file system monitor attributes for specific directories are provided
for typical UNIX 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 /lost+found
v /sbin
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
Memory v Available (bytes)
v Used (bytes)
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 Yesterday’s execution time
v Yesterday’s new executions
UNIX v CPU monitors
system
v Disk monitors
v Disk performance monitors
v Memory monitors
v Network monitors

Chapter 5. Monitoring system status and health 307

 Resource
monitor Attributes
CIM Note: The attributes for CIM monitors can vary depending on the features
and functions that you have configured on the managed system.
v Namespaces
v Classes
v Instances
v Properties

Windows resource-monitor attributes

These resource-monitor attributes are for the Windows operating system.

Note: The attributes for the following resource monitors can vary depending on
the features and functions that you have configured on the managed system:
v CIM monitors
v Device, performance, and service monitors
v Registry monitors

Resource
monitor Attributes
CPU v CPU utilization
v CPU ’x’ utilization (on SMP devices)
v Process count
Disk Note: The disk drive monitor attributes are repeated for each local
nonremovable logical drive that is found.
v Disk 1 workload
v Drive C: % space used
v Drive C: Space remaining
v Drive C: Space used
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.
v Directory
– Directory exists
– Last modified
v File
– Checksum
– File exists
– Last modified
– File size (bytes)
Memory v Locked memory
v Memory usage

308 IBMSystems Director Systems Management Guide

 Resource
monitor Attributes
TCP/IP v Interface x - Broadcast packets received
v Interface x - Broadcast packets sent
v Interface x - Bytes received
v Interface x - Bytes sent
v Interface x - Unicast packets received
v Interface x - Unicast packets sent
v IP packets received
v IP packets received with errors
v IP packets sent
v TCP connections
v UDP datagrams received
v UDP datagrams sent
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 Yesterday’s execution time
v Yesterday’s new executions
CIM v Namespaces
v Classes
v Instances
v Properties

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 using one of two methods, both of which open the
same Monitors task:
Open the Monitors task from the IBM Systems Director Web interface
navigation area:
a. In the IBM Systems Director Web interface navigation area, expand System
Status and Health → Monitors.
Open the Monitors task from Navigate Resources:
a. In the IBM Systems Director Web interface navigation area, click Navigate
Resources.
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.

Chapter 5. Monitoring system status and health 309

 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.
4. From the Monitor selection page, select the monitor view that you want to be
displayed for the targets that you selected.
5. Click Show Monitors. The Monitor View page listing monitors for the targets
that you selected is displayed.
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 will 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, versions 5.20 and 5.10.
v Common CIM monitors are available for all 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:

1. Open the Monitors task using one of two methods, both of which open the
same Monitors task:
Open the Monitors task from the IBM Systems Director Web interface
navigation area:
a. In the IBM Systems Director Web interface navigation area, expand System
Status and Health → Monitors.
Open the Monitors task from Navigate Resources:
a. In the IBM Systems Director Web interface navigation area, click Navigate
Resources.
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. 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.

310 IBMSystems Director Systems Management Guide

5. In the Show field, select Selected Resources to choose from existing monitored
resources or Monitor Views to choose from existing monitor views. The
monitors that are shipped with IBM Systems Director include the following
monitors:
Table 22. Monitors that are shipped with IBM Systems Director
Monitor name Data retrieved
Active Virtual Memory (%) Percentage of Active Virtual Memory on
your resources5a
Active Virtual Memory (4K Pages) Active Virtual Memory in 4K page unit on
your resources5a
CPU Utilization Rate at which the CPU is running5b
CPU Utilization % Percentage of CPU utilization on your
resources5c
Disk % Space Available Percentage of available disk space on your
resources
Disk % Space Used Percentage of disk space that is in use on
your resources5d
Disk 0 Workload Workload managed by disk 0
Disk Space Remaining Amount of available disk space on your
resources5d
Disk Space Used Amount of disk space that is in use on your
resources5d
Entitled Processing Units Number of entitled processing units on your
resources5c
IP Packets Received with Errors/sec Number of IP packets that contain errors
received on your resources each second
IP Packets Received/sec Number of IP packets received on your
resources each second
IP Packets Sent/sec Number of IP packets sent on your
resources each second
IPV6 Error Packets Received/sec Number of IPV6 packets that contain errors
received on your resources each second5a
IPV6 Packets Received/sec Number of IPV6 packets received on your
resources each second5a
IPV6 Packets Sent/sec Number of IPV6 packets sent on your
resources each second5a
Locked Memory Amount of memory that is locked
Memory (MB) Amount of memory, in MB, on your
resources5c
Memory Usage Memory usage on your resources5b
Paging Space Free (%) Percentage of available paging space on
your resources5a
Paging Space Remaining (4K Pages) Amount of remaining paging space on your
resources5a
Paging Space Reserved (4K Pages) Amount of reserved paging space on your
resources5a
Paging Space Total (4K Pages) Total amount of paging space on your
resources5a

Chapter 5. Monitoring system status and health 311

 Table 22. Monitors that are shipped with IBM Systems Director (continued)
Monitor name Data retrieved
Paging Space Used (%) Percentage of used paging space on your
resources5a
Paging Space Used (4K Pages) Amount of used paging space on your
resources5a
Process Count Process count on your resources
Processors Number of processors on your resources5c
TCP Connections Number of TCP connection on your
resources
UDP Datagrams Received/sec Number of UDP datagrams received on
your resources each second
UDP Datagrams Sent/sec Number of UDP datagrams sent on your
resources each second

Notes:
a. This monitor is for AIX only.
b. This monitor gathers data that is supplied by the agent.
c. This monitor is a virtualization manager monitor that is not enabled by
default.
d. On AIX, this monitor calculates only the / directory.
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 will appear in the Monitor Views table.

Editing a monitor view

Use the Monitors task to edit monitor views.

To edit a monitor view, complete the following steps:

1. Open the Monitors task using one of two methods, both of which open the
same Monitors task:
Open the Monitors task from the IBM Systems Director Web interface
navigation area:
a. In the IBM Systems Director Web interface navigation area, expand System
Status and Health → Monitors.
Open the Monitors task from Navigate Resources:
a. In the IBM Systems Director Web interface navigation area, click Navigate
Resources.
b. Either select a group or drill down to select a resource within a group.
c. Click Actions → System Status and Health → Monitors.

312 IBMSystems Director Systems Management Guide

 The Monitors task with a table listing applicable monitor views and
information about each monitor view is displayed.
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:

1. Open the Monitors task using one of two methods, both of which open the
same Monitors task:
Open the Monitors task from the IBM Systems Director Web interface
navigation area:
a. In the IBM Systems Director Web interface navigation area, expand System
Status and Health → Monitors.
Open the Monitors task from Navigate Resources:
a. In the IBM Systems Director Web interface navigation area, click Navigate
Resources.
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. 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:

1. Open the Monitors task using one of two methods, both of which open the
same Monitors task:
Open the Monitors task from the IBM Systems Director Web interface
navigation area:
a. In the IBM Systems Director Web interface navigation area, expand System
Status and Health → Monitors.
Open the Monitors task from Navigate Resources:
a. In the IBM Systems Director Web interface navigation area, click Navigate
Resources.
b. Either select a group or drill down to select a resource within a group.
c. Click Actions → System Status and Health → Monitors.

Chapter 5. Monitoring system status and health 313

 The Monitors task with a table listing applicable monitor views and
information about each monitor view is displayed.
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.

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.

To create a threshold for a specific monitor, complete the following steps:

1. Open the Monitors task using one of two methods, both of which open the
same Monitors task:
Open the Monitors task from the IBM Systems Director Web interface
navigation area:
a. In the IBM Systems Director Web interface navigation area, expand System
Status and Health → Monitors.
Open the Monitors task from Navigate Resources:
a. In the IBM Systems Director Web interface navigation area, click Navigate
Resources.
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. From the Monitor selection page, select the monitor view that you want to be
displayed for the targets that you selected.
3. Click Show Monitors. The Monitor View page listing monitors for the targets
that you selected is displayed.
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.
Related tasks
“Managing thresholds”
“Viewing a threshold” on page 315
“Activating a threshold” on page 315

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.

314 IBMSystems Director Systems Management Guide

 Related tasks
“Creating a threshold” on page 314

Viewing a threshold
Use the Thresholds task to view thresholds that are set for the monitors on your
resources or use the Navigate Resources 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:
a. In the IBM Systems Director Web interface navigation area, click Navigate
Resources.
b. Navigate to the resource for which you want to view the threshold.
c. From the Navigate Resources table, right-click the resource and select
System Status and Health → Thresholds. The Thresholds page is displayed.
Related tasks
“Creating a threshold” on page 314

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:

1. 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.
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.
Related tasks
“Creating a threshold” on page 314

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:

Chapter 5. Monitoring system status and health 315

 1. 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.
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.

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:

1. 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.
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:

1. 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.
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.

316 IBMSystems Director Systems Management Guide

 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
Navigate Resources 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

Status set entries that are reported by resources in your environment are tracked
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:

1. In the IBM Systems Director Web interface navigation area, expand System
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.
Note that 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.
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
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.

Chapter 5. Monitoring system status and health 317

 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

Status set entries that are reported by resources in your environment are tracked
by IBM Systems Director and displayed in the applicable health summary tasks
and panels. Use the Navigate Resources task to view status set entries for specific
resources.

You can view status set entries for only those resources to which you have access.

To view the status information for a specific resource, complete the following steps:
1. In the IBM Systems Director Web interface navigation area, click Navigate
Resources.
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.

You can use the Ignore, Activate, and Delete actions to control the entries that are
displayed and collected.

Viewing status set entries for a group of resources

Status set entries that are reported by resources in your environment are tracked
by IBM Systems Director and displayed in the applicable health summary tasks
and panels. Use the Navigate Resources task to view status set entries for the
resources that belong to a specific group.

You can view status set entries for only those resources to which you have access.

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.

You can use the Ignore, Activate, and Delete actions to control the entries that are
displayed and collected.

318 IBMSystems Director Systems Management Guide

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:

1. In the IBM Systems Director Web interface navigation area, expand System
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.
Note that 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.
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
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.
A table listing applicable status set entries and information about each entry is
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:

1. In the IBM Systems Director Web interface navigation area, expand System
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.

Chapter 5. Monitoring system status and health 319

 Note that 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.
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
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.
A table listing applicable status set entries and information about each entry is
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:

1. In the IBM Systems Director Web interface navigation area, expand System
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.
Note that 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.
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
manage these status set entries. You can also ignore entries to prevent IBM

320 IBMSystems Director Systems Management Guide

 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. 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.

Managing the event log

An event is an occurrence of significance to a task or resource. Examples of events
include the completion of an operation, the failure of a hardware component, or
the exceedance of a processor threshold. The Event Log task displays all events
that are received from any number of sources by IBM Systems Director Server.
Related concepts
“Events” on page 334

Viewing events
Use the Event Log task to view events that are stored in the event log.

You can view all events, events for a specific managed system 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 using one of two methods:
Open the event log from the IBM Systems Director Web interface navigation
area:
a. In the IBM Systems Director Web interface navigation area, expand System
Status and Health and click Event Log.
Open the event log from Navigate Resources:
a. In the IBM Systems Director Web interface navigation area, click Navigate
Resources.
b. Either select a group or drill down to select a resource within a group.
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.

Chapter 5. Monitoring system status and health 321

 You can use the Delete action to control the events that are displayed.

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 using one of two methods:
Open the event log from the IBM Systems Director Web interface navigation
area:
a. In the IBM Systems Director Web interface navigation area, expand System
Status and Health and click Event Log.
Open the event log from Navigate Resources:
a. In the IBM Systems Director Web interface navigation area, click Navigate
Resources.
b. Either select a group or drill down to select a resource within a group.
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.

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:

1. In the IBM Systems Director Web interface navigation area, expand Settings
and then click Event Log Preferences. The Event Log Preferences page is
displayed.
2. On the Event Log Preferences page, complete the necessary steps for the
change that you want to make:
Table 23. Event log actions
To do this task: Complete these steps:
Change the time range of the event log By default, the time range is configured to
include only the last 24 hours of reported
events. You can change the unit of time and
the time range that is used.
1. In the Time Range field, type the
number of units of time.
2. In the Time Range field, select Hours,
Days, or Weeks to indicate how the time
range is measured.
3. Click Apply.

322 IBMSystems Director Systems Management Guide

 Table 23. Event log actions (continued)
To do this task:
Change the number of events stored in the
event log
Restore the event log preferences to the
default values
Complete these steps:
By default, the event log is configured to
retrieve 500 entries.
1. In the Number of entries to retrieve
field, type the maximum number of
entries to retrieve.
2. Click Apply.
1. Click Restore Defaults.

3. When you are finished modifying the event log preferences, click OK.

Managing SNMP devices

IBM Systems Director provides tasks for configuring and managing SNMP devices
and Management Information Base (MIB) files.
Related tasks
“Starting the IBM Systems Director Launched Tasks program” on page 164
Related reference
Launched tasks troubleshooting

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.

Note: This task requires the IBM Systems Director Launched Tasks program. This
program is installed automatically the first time you use a task that requires it. For
information about the IBM Systems Director Launched Tasks program, see
“Starting the IBM Systems Director Launched Tasks program.”

To view SNMP devices, complete the following steps:

1. In the IBM Systems Director Web interface navigation area, expand System
Status and Health and then click SNMP Management.
2. On the SNMP Management page, click SNMP Browser.
3. In the Run - SNMP Browser window, select an available SNMP agent, click
Add, and then click OK. The IBM Systems Director Launched Tasks program
opens the SNMP Browser page.
4. In the Device Information pane of the SNMP Browser page, expand the tree to
view the SNMP information. Select an attribute in the Device Information pane.

The right pane splits and displays the Value and Details panes. The Value pane
displays the value of the selected attribute. The Details pane displays the
characteristics of the selected attribute, including, for example, the type and access
status of the device attribute and a description of the device attribute.

Note: To configure your SNMP devices, see “Accessing a secured system with
configure access”.

Chapter 5. Monitoring system status and health 323

 Related tasks
“Starting the IBM Systems Director Launched Tasks program” on page 164
“Accessing a secured system with configure access” on page 715

Compiling a MIB file

The SNMP Browser initially displays a tree view of the Management Information
Base (MIB) structure for the selected SNMP devices. If no compiled MIBs are
available on the management server to format the information or if the device
returns information that is not found in a compiled MIB, the information is
displayed in a dotted-decimal format. IBM Systems Director includes various MIB
files that are typically needed for SNMP browsing for commonly defined devices.

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 MIBs
that are commonly used. If you have updated the list of MIBs 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\data\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.

Note: This task requires the IBM Systems Director Launched Tasks program. This
program is installed automatically the first time you use a task that requires it. For
information about the IBM Systems Director Launched Tasks program, see
“Starting the IBM Systems Director Launched Tasks program.”

To compile a MIB file, complete the following steps:

1. In the IBM Systems Director Web interface navigation area, expand System
Status and Health and then click SNMP Management.
2. On the SNMP Management page, click Manage MIBs. The IBM Systems
Director Launched Tasks program opens the MIB Management page.
3. On the MIB Management page, click File → Select MIB to Compile.
4. On the MIB Management page, specify the directory and file name of the MIB
file that you want to compile, and click OK. A status window indicates the
progress of the compilation.
Related tasks
“Starting the IBM Systems Director Launched Tasks program” on page 164

Selecting MIB files to load into memory

If you want to select specific Management Information Base (MIB) files to load into
memory, use the MIB Management feature of the SNMP Browser.

Note: This task requires the IBM Systems Director Launched Tasks program. This
program is installed automatically the first time you use a task that requires it. For
information about the IBM Systems Director Launched Tasks program, see
“Starting the IBM Systems Director Launched Tasks program.”

324 IBMSystems Director Systems Management Guide

 To select specific MIB files to load into memory, complete the following tasks:
1. In the IBM Systems Director Web interface navigation area, expand System
Status and Health and then click SNMP Management.
2. On the SNMP Management page, click Manage MIBs. The IBM Systems
Director Launched Tasks program opens the MIB Management page.
3. On the MIB Management page, click File → Select MIB to load.
4. From the Available MIBs list, select the MIBs that you want to load into
memory.
5. Click Add to transfer the selected MIBs to the Loaded MIBs list.
6. Click OK.
Related tasks
“Starting the IBM Systems Director Launched Tasks program” on page 164

Managing process monitors

You can use process monitors to generate events when an application process
starts, stops, or fails to start.
Related tasks
“Starting the IBM Systems Director Launched Tasks program” on page 164
Related reference
Launched tasks troubleshooting

Viewing process monitors

You can view a list of the process monitors that are running on a managed system.

Note: This task requires the IBM Systems Director Launched Tasks program. This
program is installed automatically the first time you use a task that requires it. For
information about the IBM Systems Director Launched Tasks program, see
“Starting the IBM Systems Director Launched Tasks program.”

To view a list of the process monitors that are running on a managed system,
complete the following steps:
1. In the IBM Systems Director Web interface navigation area, click Navigate
Resources.
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. The Process Monitors launched task is displayed.
4. In the Process Monitors window, select the monitor that you want to view and
click View.
Related tasks
“Starting the IBM Systems Director Launched Tasks program” on page 164

Creating a process monitor

In order to monitor a process, you must create a monitor.

Note: This task requires the IBM Systems Director Launched Tasks program. This
program is installed automatically the first time you use a task that requires it. For
information about the IBM Systems Director Launched Tasks program, see
“Starting the IBM Systems Director Launched Tasks program.”

Chapter 5. Monitoring system status and health 325

 To create a process monitor, complete the following steps:
1. In the IBM Systems Director Web interface navigation area, click Navigate
Resources.
2. Navigate to the resource from which you want to create a process monitor.
3. Right-click the resource and select System Status and Health → Process
Monitors. The Process Monitors launched task is displayed.
4. In the Process Monitors window, type the executable file name of the
application process that you want to monitor.
5. Select any combination of the Start, Stop, and Fail check boxes, to specify
which action or actions you want to monitor.
6. If you selected the Fail check box, type a timeout setting. This setting is the
number of seconds that the process monitor will wait for the application
process to start before generating a fail event.
7. To monitor additional processes with the same Process Monitors subtask, click
Edit → New Row.
8. Repeat steps 4 through 7 until you have listed the executable file names of all
the processes that you want to monitor.
9. Click File → Save As to save the process monitor.
10. In the Save As window, type a name to identify the process monitor; then,
click OK.

The new process monitor is displayed as a subtask under the Process Monitors
task in IBM Systems Director Web interface.
Related tasks
“Starting the IBM Systems Director Launched Tasks program” on page 164

Applying a process monitor

In order to monitor a process, you must start the process monitor.

Note: This task requires the IBM Systems Director Launched Tasks program. This
program is installed automatically the first time you use a task that requires it. For
information about the IBM Systems Director Launched Tasks program, see
“Starting the IBM Systems Director Launched Tasks program.”

To apply a process monitor, complete the following steps:

1. In the IBM Systems Director Web interface navigation area, click Navigate
Resources.
2. Navigate to the resource to which you want to apply a process monitor.
3. From the Navigate Resources table, right-click the resource and select System
Status and Health → Manage Processes. The Manage Processes launched task is
displayed.
4. In the Manage Processes window, select the process that you want to apply to
the resource and add it to the monitor.
5. Close the Manage Processes window.
6. Right-click the resource and select System Status and Health → Process
Monitors. The Process Monitors launched task is displayed.
7. In the Process Monitor window, find the process that you added in step 4
8. Select the Start check box to start the monitor.

326 IBMSystems Director Systems Management Guide

 Related tasks
“Starting the IBM Systems Director Launched Tasks program” on page 164

Removing all process monitors

You can remove all process monitors from a managed resource.

Note: This task requires the IBM Systems Director Launched Tasks program. This
program is installed automatically the first time you use a task that requires it. For
information about the IBM Systems Director Launched Tasks program, see
“Starting the IBM Systems Director Launched Tasks program.”

To remove all process monitors from a managed resource, complete the following
steps:
1. In the IBM Systems Director Web interface navigation area, click Navigate
Resources.
2. Navigate to the resource from which you want to remove all process monitors.
3. Right-click the resource and select System Status and Health → Remove
Process Monitors. The Run window opens and the Schedule page is displayed.
4. Select Run Now and click OK, or schedule the job. For more information, see
“Scheduling tasks.”
Related tasks
“Starting the IBM Systems Director Launched Tasks program” on page 164
“Scheduling tasks” on page 199

Monitoring system resources

You can view statistics about critical system resources, such as processor, disk, and
memory usage with the All Available Recordings task. You can create event
automation plans to respond to resource-monitor events. You can apply resource
monitors to individual managed systems and devices and to groups.
Related tasks
“Starting the IBM Systems Director Launched Tasks program” on page 164
Related reference
Launched tasks troubleshooting

Recording resource-monitor statistics

You can record a resource monitor to capture statistics about a managed system.

Note: This task requires the IBM Systems Director Launched Tasks program. This
program is installed automatically the first time you use a task that requires it. For
information about the IBM Systems Director Launched Tasks program, see
“Starting the IBM Systems Director Launched Tasks program.”

Note: You can set and record resource-monitor statistics for only individual
managed systems or devices. You cannot record resource-monitor statistics for a
group.
1. In the IBM Systems Director Web interface navigation area, click Navigate
Resources to locate the resource for which you want to set and record
resource-monitor statistics.
2. Right-click the resource and select System Status and Health → Monitors.
3. Select a view from the list of views.

Chapter 5. Monitoring system status and health 327

 4. From the list of monitors displayed, right-click the monitor you want to record
and click Resource Monitor Recording.
5. On the Resource Monitor Recording page, click File → New.
6. On the New Record page, type a description and select the length of time to
record the resource monitor.
7. Click OK to start recording.
8. Click View → Refresh to update the status of the recording.
Related tasks
“Starting the IBM Systems Director Launched Tasks program” on page 164

Exporting resource-monitor statistics

You can export a resource-monitor record to a file in text, comma separated values
(CSV), HTML, or XML format for the purpose of archiving statistics.

Note: This task requires the IBM Systems Director Launched Tasks program. This
program is installed automatically the first time you use a task that requires it. For
information about the IBM Systems Director Launched Tasks program, see
“Starting the IBM Systems Director Launched Tasks program.”

Complete the following steps to export a resource-monitor record:

1. In the IBM Systems Director navigation area, click Navigate Resources to locate
the resource from which you want to export a resource-monitor record.
2. Right-click the resource and select System Status and Health → All Available
Recordings.
3. In the All Available Recordings window, right-click the record that you want to
export.
4. Click Export.
5. In the Export window, select the drive and directory, type a name for the file,
select the file type, and click OK.

Note: You can save the file only to a file system that is accessible from the
system running IBM Systems Director Server.
Related tasks
“Starting the IBM Systems Director Launched Tasks program” on page 164

Viewing a graph of a resource-monitor recording

You can view a graph of a resource-monitor recording.

Note: This task requires the IBM Systems Director Launched Tasks program. This
program is installed automatically the first time you use a task that requires it. For
information about the IBM Systems Director Launched Tasks program, see
“Starting the IBM Systems Director Launched Tasks program.”

To view a graph of a resource-monitor recording, complete the following steps:

1. In the IBM Systems Director Web interface navigation area, click Navigate
Resources to locate the managed system for which you want to review the
recordings.
2. Right-click the resource and select System Status and Health → All Available
Recordings.

328 IBMSystems Director Systems Management Guide

 3. In the All Available Recordings window, locate the recording that you want to
review; then, right-click the cell and click Graph to display a graph of the
recorded data.
Related tasks
“Starting the IBM Systems Director Launched Tasks program” on page 164

Removing a resource-monitor record

You can remove a resource-monitor record for a managed system.

Note: This task requires the IBM Systems Director Launched Tasks program. This
program is installed automatically the first time you use a task that requires it. For
information about the IBM Systems Director Launched Tasks program, see
“Starting the IBM Systems Director Launched Tasks program.”

To remove a resource-monitor record, complete the following steps:

1. In the IBM Systems Director Web interface navigation area, click Navigate
Resources to locate the resource from which you want to remove a
resource-monitor record.
2. Right-click the resource and select System Status and Health → All Available
Recordings.
3. Select one or more records to delete.
4. Click Edit → Delete.
5. Click Yes to confirm the deletion.
Related tasks
“Starting the IBM Systems Director Launched Tasks program” on page 164

Running a command-line program on a managed system

You can define a command-line program to run on a managed system. Anonymous
command restrictions apply to command definitions.

Creating a command definition

You can use command automation to run a command-line program on a managed
system. A command definition can be run immediately, scheduled to run at a
specific time, or scheduled to run at regular intervals.

Note: This task requires the IBM Systems Director Launched Tasks program. This
program is installed automatically the first time you use a task that requires it. For
information about the IBM Systems Director Launched Tasks program, see
“Starting the IBM Systems Director Launched Tasks program.”

Note: 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 a command definition, complete the following steps:

1. In the IBM Systems Director Web interface navigation area, click Navigate
Resources.
2. Navigate to the resource for which you want to create a command definition.
3. Right-click the resource and select Automation → Command Automation. The
Command Automation page is displayed.
4. Click Create.

Chapter 5. Monitoring system status and health 329

 5. Specify information about the command-line operation:
a. In the Command 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), you can specify the command to run in the following manner:
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
b. In the Timeout field, type a timeout value, in seconds. Make sure that the
timeout value is long enough.
c. Select the Log check box if the command produces text-based output, for
example, a directory listing.
d. Optional: If you want to run the process using an alternate 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 using
Application Administration in Power Systems Navigator.

Note: You either must specify an alternate 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.
6. Click File → Save As to save the command definition.
7. In the Save As window, type a name.

Note: The name for a command definition includes the following information:
v Type of command definition that is to be run
v Name of the command definition that is to be run
v Types of managed systems with which the command definition will work
correctly
8. Click OK.
9. Click File → Close to close the window.

The new command definition is displayed on the Command Automation page in

the IBM Systems Director Web interface.

330 IBMSystems Director Systems Management Guide

 Related tasks
“Starting the IBM Systems Director Launched Tasks program” on page 164
Related reference
Launched tasks troubleshooting

Running a command definition

After creating a command definition, you can run that command definition on a
selected resource.

As an alternative to using the Command Definition task in the IBM Systems

Director Web interface, you also can specify the command definition as an action
in an event automation plan.

Note: Using the Command Automation task to launch interactive programs, for
example notepad.exe, is not supported.

To run a command definition, complete the following steps:

1. In the IBM Systems Director Web interface navigation area, click Navigate
Resources.
2. Navigate to the resource on which you want to run the command definition.
3. Right-click the resource and select Automation → Command Automation. The
Command Automation page is displayed.
4. Select the command definition that you want to run.
5. Click Run.

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\IBM\
Director\CurrentVersion.

Chapter 5. Monitoring system status and health 331

 3. Double-click RestrictAnonCmdExec.
4. In the Value data field, change 0 to 1.
5. Click OK. The change takes effect immediately.

332 IBMSystems Director Systems Management Guide

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
Director Web interface.

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.”

© Copyright IBM Corp. 1999, 2009 333

 Related concepts
eLearning: Automating tasks
Related tasks
Chapter 5, “Monitoring system status and health,” on page 285
“Creating an event automation plan” on page 364
Related reference
System status and health troubleshooting
Planning for events
Event and event automation plan commands

Events, filters, and actions in event automation plans

An event automation plan is composed of two components: 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.

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 IBM 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 IBM® service processor notifications through out-of-band communication.

When IBM Systems Director Server receives these events or notifications, it

converts them into IBM Systems Director events. For example, when IBM Systems
Director Server receives a CIM indication, it converts the CIM indication into an
IBM Systems Director event of the type CIM.

334 IBMSystems Director Systems Management Guide

 Note: IBM Systems Director can convert CIM indications into other event types,
including event types that are used by enterprise-level system-management
programs, such as SNMP events. Using these event types, IBM Systems Director
can provide system data to the enterprise-level system-management programs
through the IBM Systems Director Upward Integration Modules. For more
information, see “CIM indications in IBM Systems Director” in the IBM Systems
Director Events Reference.

However, these SNMP events are not the same as SNMP traps that IBM Systems
Director Server receives out-of-band (that is, not through Common Agent or
Platform Agent). Out-of-band SNMP traps are generated by hardware products
and other software programs. They are displayed under the SNMP node in the
Event Filter Builder tree, but beneath a different subnode.

Alerts and resolutions

In IBM 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”
“Event actions” on page 340
Related reference
CIM indications in IBM Systems Director

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.

Chapter 6. Automating tasks 335

 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 334
“Event actions” on page 340

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.
Related concepts
“Simple event filter”
“Duplication event filter” on page 338
“Exclusion event filter” on page 339
“Threshold event filter” on page 339

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.

336 IBMSystems Director Systems Management Guide

Common Agent offline
Processes only those events that are generated by the Common Agent
when it 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.

Chapter 6. Automating tasks 337

 Related concepts
“Events that are available for filtering” on page 336
“Duplication event filter”
“Exclusion event filter” on page 339
“Threshold event filter” on page 339
Related tasks
“Copying an event filter” on page 401
“Viewing predefined filter criteria” on page 402

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.

338 IBMSystems Director Systems Management Guide

Related concepts
“Events that are available for filtering” on page 336
“Simple event filter” on page 336
“Exclusion event filter”
“Threshold event filter”

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.

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.

For example, using this filter type you can monitor the Windows Security event
log events, but exclude security alerts 528, 551, and 552.
Related concepts
“Events that are available for filtering” on page 336
“Simple event filter” on page 336
“Duplication event filter” on page 338
“Threshold event filter”

Threshold event filter

In addition to the simple filter options, a threshold 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 threshold 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 threshold 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.

Chapter 6. Automating tasks 339

 Related concepts
“Events that are available for filtering” on page 336
“Simple event filter” on page 336
“Duplication event filter” on page 338
“Exclusion event filter” on page 339

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 concepts
“Events” on page 334
“Event filters” on page 335
Related tasks
“Creating an event action” on page 382
“Editing an event action” on page 383
“Copying an event action” on page 384
“Deleting an event action” on page 386
“Activating and deactivating an event-action history” on page 387
“Viewing an event-action history” on page 388
“Viewing event action properties” on page 390

Send an alphanumeric page (using TAP)

(Windows only) Sends a message to a pager using the Telocator Alphanumeric
Protocol (TAP).
Requirements
This event action has the following requirements:
v The management server must be running the Windows operating
system.
v Pager network service must be available.
v The management server must have access to a modem.
Result The specified number is paged and receives the alphanumeric message.

340 IBMSystems Director Systems Management Guide

Example
Use this event action to send a message to service personnel when a
printer jams and fails.

Note: You can use event-data-substitution variables to include event data

information into the alphanumeric message. For more information, see
“Event-data-substitution variables.”
Related concepts
“Event-data-substitution variables” on page 391
“Send an e-mail (Internet SMTP) ”
“Send an e-mail to a mobile phone” on page 342
“Start a program on a system” on page 343
“Start a program on the system that generated the event” on page 344
“Start a program on the management server” on page 345
“Log to a log file” on page 346
“Modify an event and send it” on page 347
“Post to a newsgroup (NNTP)” on page 348
“Send a numeric page” on page 349
“Send a Tivoli Enterprise Console event” on page 350
“Send an SNMP INFORM request to an IP host” on page 351
“Send an SNMP trap reliably to a NetView host” on page 352
“Send an SNMP trap to an IP host” on page 353
“Set an event system variable” on page 354
“Start a task on a specified system” on page 355
“Start a task on the system that generated the event” on page 356
“Static group: add or remove group members” on page 357
“Static group: add or remove the event-generating system” on page 358
“Timed alarm that generates an event” on page 359
“Timed alarm that starts a program” on page 360
Related tasks
“Testing an event action” on page 385

Send an e-mail (Internet SMTP)

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.

Note: You can use event-data-substitution variables to include event data

information in the subject and body of the e-mail message. For more
information, see “Event-data-substitution variables.”
Chapter 6. Automating tasks 341
 Related concepts
“Event-data-substitution variables” on page 391
“Send an alphanumeric page (using TAP)” on page 340
“Send an e-mail to a mobile phone”
“Start a program on a system” on page 343
“Start a program on the system that generated the event” on page 344
“Start a program on the management server” on page 345
“Log to a log file” on page 346
“Modify an event and send it” on page 347
“Post to a newsgroup (NNTP)” on page 348
“Send a numeric page” on page 349
“Send a Tivoli Enterprise Console event” on page 350
“Send an SNMP INFORM request to an IP host” on page 351
“Send an SNMP trap reliably to a NetView host” on page 352
“Send an SNMP trap to an IP host” on page 353
“Set an event system variable” on page 354
“Start a task on a specified system” on page 355
“Start a task on the system that generated the event” on page 356
“Static group: add or remove group members” on page 357
“Static group: add or remove the event-generating system” on page 358
“Timed alarm that generates an event” on page 359
“Timed alarm that starts a program” on page 360
Related tasks
“Testing an event action” on page 385

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.

Note: You can use event-data-substitution variables to include event data

information in the subject and body of the e-mail message. For more
information, see “Event-data-substitution variables.”

342 IBMSystems Director Systems Management Guide

Related concepts
“Event-data-substitution variables” on page 391
“Send an alphanumeric page (using TAP)” on page 340
“Send an e-mail (Internet SMTP) ” on page 341
“Start a program on a system”
“Start a program on the system that generated the event” on page 344
“Start a program on the management server” on page 345
“Log to a log file” on page 346
“Modify an event and send it” on page 347
“Post to a newsgroup (NNTP)” on page 348
“Send a numeric page” on page 349
“Send a Tivoli Enterprise Console event” on page 350
“Send an SNMP INFORM request to an IP host” on page 351
“Send an SNMP trap reliably to a NetView host” on page 352
“Send an SNMP trap to an IP host” on page 353
“Set an event system variable” on page 354
“Start a task on a specified system” on page 355
“Start a task on the system that generated the event” on page 356
“Static group: add or remove group members” on page 357
“Static group: add or remove the event-generating system” on page 358
“Timed alarm that generates an event” on page 359
“Timed alarm that starts a program” on page 360
Related tasks
“Testing an event action” on page 385

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
This event action requires that the specified system have Common Agent
installed.
Result The program is started on the specified system.
Example
You can create an event automation plan that detects a critical Ambient
Temperature threshold event from Active Energy Manager on a system
running Windows 2003. Using this action, you can start the shutdown.exe
program on other systems in the same location that are running operating
systems that Active Energy Manager does not support, such as Windows
Vista.

Tip: You can use event-data-substitution variables in the Program file

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

Chapter 6. Automating tasks 343

 Related concepts
“Event-data-substitution variables” on page 391
“Send an alphanumeric page (using TAP)” on page 340
“Send an e-mail (Internet SMTP) ” on page 341
“Send an e-mail to a mobile phone” on page 342
“Start a program on the system that generated the event”
“Start a program on the management server” on page 345
“Log to a log file” on page 346
“Modify an event and send it” on page 347
“Post to a newsgroup (NNTP)” on page 348
“Send a numeric page” on page 349
“Send a Tivoli Enterprise Console event” on page 350
“Send an SNMP INFORM request to an IP host” on page 351
“Send an SNMP trap reliably to a NetView host” on page 352
“Send an SNMP trap to an IP host” on page 353
“Set an event system variable” on page 354
“Start a task on a specified system” on page 355
“Start a task on the system that generated the event” on page 356
“Static group: add or remove group members” on page 357
“Static group: add or remove the event-generating system” on page 358
“Timed alarm that generates an event” on page 359
“Timed alarm that starts a program” on page 360
Related tasks
“Testing an event action” on page 385

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
This event action requires that the specified system have Common Agent
installed.
Result The program is started on the specified system.
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.

344 IBMSystems Director Systems Management Guide

 Tip: You can use event-data-substitution variables in the Program file
name field. For more information, see “Event-data-substitution variables.”
Related concepts
“Event-data-substitution variables” on page 391
“Send an alphanumeric page (using TAP)” on page 340
“Send an e-mail (Internet SMTP) ” on page 341
“Send an e-mail to a mobile phone” on page 342
“Start a program on a system” on page 343
“Start a program on the management server”
“Log to a log file” on page 346
“Modify an event and send it” on page 347
“Post to a newsgroup (NNTP)” on page 348
“Send a numeric page” on page 349
“Send a Tivoli Enterprise Console event” on page 350
“Send an SNMP INFORM request to an IP host” on page 351
“Send an SNMP trap reliably to a NetView host” on page 352
“Send an SNMP trap to an IP host” on page 353
“Set an event system variable” on page 354
“Start a task on a specified system” on page 355
“Start a task on the system that generated the event” on page 356
“Static group: add or remove group members” on page 357
“Static group: add or remove the event-generating system” on page 358
“Timed alarm that generates an event” on page 359
“Timed alarm that starts a program” on page 360

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
None
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.”

Chapter 6. Automating tasks 345

 Related concepts
“Event-data-substitution variables” on page 391
“Send an alphanumeric page (using TAP)” on page 340
“Send an e-mail (Internet SMTP) ” on page 341
“Send an e-mail to a mobile phone” on page 342
“Start a program on a system” on page 343
“Start a program on the system that generated the event” on page 344
“Log to a log file”
“Modify an event and send it” on page 347
“Post to a newsgroup (NNTP)” on page 348
“Send a numeric page” on page 349
“Send a Tivoli Enterprise Console event” on page 350
“Send an SNMP INFORM request to an IP host” on page 351
“Send an SNMP trap reliably to a NetView host” on page 352
“Send an SNMP trap to an IP host” on page 353
“Set an event system variable” on page 354
“Start a task on a specified system” on page 355
“Start a task on the system that generated the event” on page 356
“Static group: add or remove group members” on page 357
“Static group: add or remove the event-generating system” on page 358
“Timed alarm that generates an event” on page 359
“Timed alarm that starts a program” on page 360
Related tasks
“Testing an event action” on page 385

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.

346 IBMSystems Director Systems Management Guide

 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 391
“Send an alphanumeric page (using TAP)” on page 340
“Send an e-mail (Internet SMTP) ” on page 341
“Send an e-mail to a mobile phone” on page 342
“Start a program on a system” on page 343
“Start a program on the system that generated the event” on page 344
“Start a program on the management server” on page 345
“Modify an event and send it”
“Post to a newsgroup (NNTP)” on page 348
“Send a numeric page” on page 349
“Send a Tivoli Enterprise Console event” on page 350
“Send an SNMP INFORM request to an IP host” on page 351
“Send an SNMP trap reliably to a NetView host” on page 352
“Send an SNMP trap to an IP host” on page 353
“Set an event system variable” on page 354
“Start a task on a specified system” on page 355
“Start a task on the system that generated the event” on page 356
“Static group: add or remove group members” on page 357
“Static group: add or remove the event-generating system” on page 358
“Timed alarm that generates an event” on page 359
“Timed alarm that starts a program” on page 360

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.
Chapter 6. Automating tasks 347
 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
“Event-data-substitution variables” on page 391
“Send an alphanumeric page (using TAP)” on page 340
“Send an e-mail (Internet SMTP) ” on page 341
“Send an e-mail to a mobile phone” on page 342
“Start a program on a system” on page 343
“Start a program on the system that generated the event” on page 344
“Start a program on the management server” on page 345
“Log to a log file” on page 346
“Post to a newsgroup (NNTP)”
“Send a numeric page” on page 349
“Send a Tivoli Enterprise Console event” on page 350
“Send an SNMP INFORM request to an IP host” on page 351
“Send an SNMP trap reliably to a NetView host” on page 352
“Send an SNMP trap to an IP host” on page 353
“Set an event system variable” on page 354
“Start a task on a specified system” on page 355
“Start a task on the system that generated the event” on page 356
“Static group: add or remove group members” on page 357
“Static group: add or remove the event-generating system” on page 358
“Timed alarm that generates an event” on page 359
“Timed alarm that starts a program” on page 360

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.”

348 IBMSystems Director Systems Management Guide

Related concepts
“Event-data-substitution variables” on page 391
“Send an alphanumeric page (using TAP)” on page 340
“Send an e-mail (Internet SMTP) ” on page 341
“Send an e-mail to a mobile phone” on page 342
“Start a program on a system” on page 343
“Start a program on the system that generated the event” on page 344
“Start a program on the management server” on page 345
“Log to a log file” on page 346
“Modify an event and send it” on page 347
“Send a numeric page”
“Send a Tivoli Enterprise Console event” on page 350
“Send an SNMP INFORM request to an IP host” on page 351
“Send an SNMP trap reliably to a NetView host” on page 352
“Send an SNMP trap to an IP host” on page 353
“Set an event system variable” on page 354
“Start a task on a specified system” on page 355
“Start a task on the system that generated the event” on page 356
“Static group: add or remove group members” on page 357
“Static group: add or remove the event-generating system” on page 358
“Timed alarm that generates an event” on page 359
“Timed alarm that starts a program” on page 360

Send a numeric page

(Windows only) Sends a numeric-only message to the specified pager.

Note: If you want to include a text message in the page and your pager supports
alphanumeric pages, use the Send an alphanumeric page (using TAP) event action.
Requirements
This event action has the following requirements:
v The management server must be running the Windows operating
system.
v Pager network service must be available.
v The management server must have access to a modem.
Result The specified number is paged and receives the numeric message.
Example
Use this event action when you want to send a pager notification to
someone. For example, if the processor use reaches 90% on a server
running critical Web applications, you might want to send a pager
notification to the server administrator so that person is aware of the
problem and can handle the problem immediately.

Chapter 6. Automating tasks 349

 Related concepts
“Send an alphanumeric page (using TAP)” on page 340
“Send an e-mail (Internet SMTP) ” on page 341
“Send an e-mail to a mobile phone” on page 342
“Start a program on a system” on page 343
“Start a program on the system that generated the event” on page 344
“Start a program on the management server” on page 345
“Log to a log file” on page 346
“Modify an event and send it” on page 347
“Post to a newsgroup (NNTP)” on page 348
“Send a Tivoli Enterprise Console event”
“Send an SNMP INFORM request to an IP host” on page 351
“Send an SNMP trap reliably to a NetView host” on page 352
“Send an SNMP trap to an IP host” on page 353
“Set an event system variable” on page 354
“Start a task on a specified system” on page 355
“Start a task on the system that generated the event” on page 356
“Static group: add or remove group members” on page 357
“Static group: add or remove the event-generating system” on page 358
“Timed alarm that generates an event” on page 359
“Timed alarm that starts a program” on page 360

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.

350 IBMSystems Director Systems Management Guide

Related concepts
“Send an alphanumeric page (using TAP)” on page 340
“Send an e-mail (Internet SMTP) ” on page 341
“Send an e-mail to a mobile phone” on page 342
“Start a program on a system” on page 343
“Start a program on the system that generated the event” on page 344
“Start a program on the management server” on page 345
“Log to a log file” on page 346
“Modify an event and send it” on page 347
“Post to a newsgroup (NNTP)” on page 348
“Send a numeric page” on page 349
“Send an SNMP INFORM request to an IP host”
“Send an SNMP trap reliably to a NetView host” on page 352
“Send an SNMP trap to an IP host” on page 353
“Set an event system variable” on page 354
“Start a task on a specified system” on page 355
“Start a task on the system that generated the event” on page 356
“Static group: add or remove group members” on page 357
“Static group: add or remove the event-generating system” on page 358
“Timed alarm that generates an event” on page 359
“Timed alarm that starts a program” on page 360

Send an SNMP INFORM request to an IP host

Sends an SNMP 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.
Requirements
This event action requires that an SNMP agent that can receive an SNMP
INFORM be installed on the specified system.
Result The specified system receives an SNMP INFORM.
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 will know whether the SNMP
INFORM was delivered successfully.

Chapter 6. Automating tasks 351

 Related concepts
“Send an alphanumeric page (using TAP)” on page 340
“Send an e-mail (Internet SMTP) ” on page 341
“Send an e-mail to a mobile phone” on page 342
“Start a program on a system” on page 343
“Start a program on the system that generated the event” on page 344
“Start a program on the management server” on page 345
“Log to a log file” on page 346
“Modify an event and send it” on page 347
“Post to a newsgroup (NNTP)” on page 348
“Send a numeric page” on page 349
“Send a Tivoli Enterprise Console event” on page 350
“Send an SNMP trap reliably to a NetView host”
“Send an SNMP trap to an IP host” on page 353
“Set an event system variable” on page 354
“Start a task on a specified system” on page 355
“Start a task on the system that generated the event” on page 356
“Static group: add or remove group members” on page 357
“Static group: add or remove the event-generating system” on page 358
“Timed alarm that generates an event” on page 359
“Timed alarm that starts a program” on page 360

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.

352 IBMSystems Director Systems Management Guide

Related concepts
“Send an alphanumeric page (using TAP)” on page 340
“Send an e-mail (Internet SMTP) ” on page 341
“Send an e-mail to a mobile phone” on page 342
“Start a program on a system” on page 343
“Start a program on the system that generated the event” on page 344
“Start a program on the management server” on page 345
“Log to a log file” on page 346
“Modify an event and send it” on page 347
“Post to a newsgroup (NNTP)” on page 348
“Send a numeric page” on page 349
“Send a Tivoli Enterprise Console event” on page 350
“Send an SNMP INFORM request to an IP host” on page 351
“Send an SNMP trap to an IP host”
“Set an event system variable” on page 354
“Start a task on a specified system” on page 355
“Start a task on the system that generated the event” on page 356
“Static group: add or remove group members” on page 357
“Static group: add or remove the event-generating system” on page 358
“Timed alarm that generates an event” on page 359
“Timed alarm that starts a program” on page 360
Related reference
lsevtacthist command

Send an SNMP trap to an IP host

Generates an SNMPv1 or SNMPv2c trap and sends it to a specified IP address or
host name.
Requirements
This event action requires that SNMP agent be available on the specified
system to receive the traps.
Result The specified system receives an SNMP trap.
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.

Chapter 6. Automating tasks 353

 Related concepts
“Send an alphanumeric page (using TAP)” on page 340
“Send an e-mail (Internet SMTP) ” on page 341
“Send an e-mail to a mobile phone” on page 342
“Start a program on a system” on page 343
“Start a program on the system that generated the event” on page 344
“Start a program on the management server” on page 345
“Log to a log file” on page 346
“Modify an event and send it” on page 347
“Post to a newsgroup (NNTP)” on page 348
“Send a numeric page” on page 349
“Send a Tivoli Enterprise Console event” on page 350
“Send an SNMP INFORM request to an IP host” on page 351
“Send an SNMP trap reliably to a NetView host” on page 352
“Set an event system variable”
“Start a task on a specified system” on page 355
“Start a task on the system that generated the event” on page 356
“Static group: add or remove group members” on page 357
“Static group: add or remove the event-generating system” on page 358
“Timed alarm that generates an event” on page 359
“Timed alarm that starts a program” on page 360

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 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

354 IBMSystems Director Systems Management Guide

 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
“Event-data-substitution variables” on page 391
“Send an alphanumeric page (using TAP)” on page 340
“Send an e-mail (Internet SMTP) ” on page 341
“Send an e-mail to a mobile phone” on page 342
“Start a program on a system” on page 343
“Start a program on the system that generated the event” on page 344
“Start a program on the management server” on page 345
“Log to a log file” on page 346
“Modify an event and send it” on page 347
“Post to a newsgroup (NNTP)” on page 348
“Send a numeric page” on page 349
“Send a Tivoli Enterprise Console event” on page 350
“Send an SNMP INFORM request to an IP host” on page 351
“Send an SNMP trap reliably to a NetView host” on page 352
“Send an SNMP trap to an IP host” on page 353
“Start a task on a specified system”
“Start a task on the system that generated the event” on page 356
“Static group: add or remove group members” on page 357
“Static group: add or remove the event-generating system” on page 358
“Timed alarm that generates an event” on page 359
“Timed alarm that starts a program” on page 360

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
This event action has the following requirements:
v The specified system must have Common Agent installed.
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.

Chapter 6. Automating tasks 355

 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.
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 concepts
“Send an alphanumeric page (using TAP)” on page 340
“Send an e-mail (Internet SMTP) ” on page 341
“Send an e-mail to a mobile phone” on page 342
“Start a program on a system” on page 343
“Start a program on the system that generated the event” on page 344
“Start a program on the management server” on page 345
“Log to a log file” on page 346
“Modify an event and send it” on page 347
“Post to a newsgroup (NNTP)” on page 348
“Send a numeric page” on page 349
“Send a Tivoli Enterprise Console event” on page 350
“Send an SNMP INFORM request to an IP host” on page 351
“Send an SNMP trap reliably to a NetView host” on page 352
“Send an SNMP trap to an IP host” on page 353
“Set an event system variable” on page 354
“Start a task on the system that generated the event”
“Static group: add or remove group members” on page 357
“Static group: add or remove the event-generating system” on page 358
“Timed alarm that generates an event” on page 359
“Timed alarm that starts a program” on page 360
Related tasks
“Testing an event action” on page 385

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
This event action has the following requirements:
v The specified system must have Common Agent installed.
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.

356 IBMSystems Director Systems Management Guide

 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.
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 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 concepts
“Send an alphanumeric page (using TAP)” on page 340
“Send an e-mail (Internet SMTP) ” on page 341
“Send an e-mail to a mobile phone” on page 342
“Start a program on a system” on page 343
“Start a program on the system that generated the event” on page 344
“Start a program on the management server” on page 345
“Log to a log file” on page 346
“Modify an event and send it” on page 347
“Post to a newsgroup (NNTP)” on page 348
“Send a numeric page” on page 349
“Send a Tivoli Enterprise Console event” on page 350
“Send an SNMP INFORM request to an IP host” on page 351
“Send an SNMP trap reliably to a NetView host” on page 352
“Send an SNMP trap to an IP host” on page 353
“Set an event system variable” on page 354
“Start a task on a specified system” on page 355
“Static group: add or remove group members”
“Static group: add or remove the event-generating system” on page 358
“Timed alarm that generates an event” on page 359
“Timed alarm that starts a program” on page 360

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

Chapter 6. Automating tasks 357

 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 source or target
group names. Doing so lets you dynamically set the source or target group
to the static group that contains the system that generated the event. For
more information, see “Event-data-substitution variables.”
Related concepts
“Event-data-substitution variables” on page 391
“Send an alphanumeric page (using TAP)” on page 340
“Send an e-mail (Internet SMTP) ” on page 341
“Send an e-mail to a mobile phone” on page 342
“Start a program on a system” on page 343
“Start a program on the system that generated the event” on page 344
“Start a program on the management server” on page 345
“Log to a log file” on page 346
“Modify an event and send it” on page 347
“Post to a newsgroup (NNTP)” on page 348
“Send a numeric page” on page 349
“Send a Tivoli Enterprise Console event” on page 350
“Send an SNMP INFORM request to an IP host” on page 351
“Send an SNMP trap reliably to a NetView host” on page 352
“Send an SNMP trap to an IP host” on page 353
“Set an event system variable” on page 354
“Start a task on a specified system” on page 355
“Start a task on the system that generated the event” on page 356
“Static group: add or remove the event-generating system”
“Timed alarm that generates an event” on page 359
“Timed alarm that starts a program” on page 360

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.

358 IBMSystems Director Systems Management Guide

 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. Doing so lets you 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
“Event-data-substitution variables” on page 391
“Send an alphanumeric page (using TAP)” on page 340
“Send an e-mail (Internet SMTP) ” on page 341
“Send an e-mail to a mobile phone” on page 342
“Start a program on a system” on page 343
“Start a program on the system that generated the event” on page 344
“Start a program on the management server” on page 345
“Log to a log file” on page 346
“Modify an event and send it” on page 347
“Post to a newsgroup (NNTP)” on page 348
“Send a numeric page” on page 349
“Send a Tivoli Enterprise Console event” on page 350
“Send an SNMP INFORM request to an IP host” on page 351
“Send an SNMP trap reliably to a NetView host” on page 352
“Send an SNMP trap to an IP host” on page 353
“Set an event system variable” on page 354
“Start a task on a specified system” on page 355
“Start a task on the system that generated the event” on page 356
“Static group: add or remove group members” on page 357
“Timed alarm that generates an event”
“Timed alarm that starts a program” on page 360

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.
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.

Chapter 6. Automating tasks 359

 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
information, see “Event-data-substitution variables.”
Related concepts
“Event-data-substitution variables” on page 391
“Send an alphanumeric page (using TAP)” on page 340
“Send an e-mail (Internet SMTP) ” on page 341
“Send an e-mail to a mobile phone” on page 342
“Start a program on a system” on page 343
“Start a program on the system that generated the event” on page 344
“Start a program on the management server” on page 345
“Log to a log file” on page 346
“Modify an event and send it” on page 347
“Post to a newsgroup (NNTP)” on page 348
“Send a numeric page” on page 349
“Send a Tivoli Enterprise Console event” on page 350
“Send an SNMP INFORM request to an IP host” on page 351
“Send an SNMP trap reliably to a NetView host” on page 352
“Send an SNMP trap to an IP host” on page 353
“Set an event system variable” on page 354
“Start a task on a specified system” on page 355
“Start a task on the system that generated the event” on page 356
“Static group: add or remove group members” on page 357
“Static group: add or remove the event-generating system” on page 358
“Timed alarm that starts a program”

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
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, 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.

360 IBMSystems Director Systems Management Guide

 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
information, see “Event-data-substitution variables.”
Related concepts
“Event-data-substitution variables” on page 391
“Send an alphanumeric page (using TAP)” on page 340
“Send an e-mail (Internet SMTP) ” on page 341
“Send an e-mail to a mobile phone” on page 342
“Start a program on a system” on page 343
“Start a program on the system that generated the event” on page 344
“Start a program on the management server” on page 345
“Log to a log file” on page 346
“Modify an event and send it” on page 347
“Post to a newsgroup (NNTP)” on page 348
“Send a numeric page” on page 349
“Send a Tivoli Enterprise Console event” on page 350
“Send an SNMP INFORM request to an IP host” on page 351
“Send an SNMP trap reliably to a NetView host” on page 352
“Send an SNMP trap to an IP host” on page 353
“Set an event system variable” on page 354
“Start a task on a specified system” on page 355
“Start a task on the system that generated the event” on page 356
“Static group: add or remove group members” on page 357
“Static group: add or remove the event-generating system” on page 358
“Timed alarm that generates an event” on page 359

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 v Windows event log

types 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

Chapter 6. Automating tasks 361

 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 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.

When IBM Systems Director starts on a system running IBM i, the process is the
same with comparable code to twgescli.exe that is included in IBM Systems
Director for IBM i.

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:

1. In the IBM Systems Director navigation area, click Welcome.
2. On the Welcome page, click the Manage tab.
3. On the Manage 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 Scheduler task page. Using
Scheduler 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.

362 IBMSystems Director Systems Management Guide

 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.

You also can reach the summary page by using Find a Task. For more information,
see “Finding a task.”

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 reference
Event automation plan commands
Exporting event automation plans (lsevtautopln command)
Generating events for testing purposes (genevent command)

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,

complete the following steps:
1. Navigate to the resource and select it.
2. Click Actions → Properties.
3. On the Properties page, click the Applied Activities tab.

Chapter 6. Automating tasks 363

 On the Applied Activities page, you can view a list of any event automation plans
that can potentially affect the resource.
Related tasks
“Creating an event automation plan”
“Copying an event automation plan” on page 378
“Editing an event automation plan” on page 379
“Deactivating and activating an event automation plan” on page 380
“Viewing event automation plan properties” on page 381
“Deleting an event automation plan” on page 381

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.
Related tasks
“Viewing event automation plans associated with a resource” on page 363
“Copying an event automation plan” on page 378
“Editing an event automation plan” on page 379
“Deactivating and activating an event automation plan” on page 380
“Viewing event automation plan properties” on page 381
“Deleting an event automation plan” on page 381
Related reference
mkevtautopln command

Beginning an event automation plan

Begin an event automation plan by giving it a name and identifying the systems
that you want the plan to monitor for specific events.

To create and begin an 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. In the Event Automation Plan wizard, the Welcome page is displayed. 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 the event automation plan will
monitor for specific generated events. Select the systems in the Available list
and click Add > to move them to the Selected list. Click Next.

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.

364 IBMSystems Director Systems Management Guide

The types of events from which you can select and the ways that you can filter the
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. Not only can you specify
additional events, but you also can create more sophisticated event filters that are
triggered when duplicates of an event are received, when a specific number of
instances of an event is received over a range of time, or when a specific event is
received but you want to exclude another event. For information about specifying
specific events, see “Selecting specific events for filtering.” For more information
about event filters, see “Event filters.”

Note: This task requires the IBM Systems Director Launched Tasks program. This
program is installed automatically the first time you use a task that requires it. For
information about the IBM Systems Director Launched Tasks program, see
“Starting the IBM Systems Director Launched Tasks program.”
Related concepts
“Event filters” on page 335
“Events that are available for filtering” on page 336
“Simple event filter” on page 336
“Duplication event filter” on page 338
“Exclusion event filter” on page 339
“Threshold event filter” on page 339
Related tasks
“Selecting common categories of events for filtering”
“Selecting specific events for filtering” on page 371

Selecting common categories of events for filtering:

You can select the events that you want to filter. When these events occur, your
event automation plan can respond with one or more customized event actions.
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.” For more information
about advanced event filters, see “Selecting specific events for filtering.”

Complete the following steps to select common categories of events for filtering in
your event automation plan:
1. On the Events page, select Common from the Events list.
2. In the Event types list, select the categories of common events that you want to
monitor. You can select more than one category of events; however, you must

Chapter 6. Automating tasks 365

 provide information for some of the categories. Provide this information before
you select another category of events. The following list describes the categories
of common events that you can select as well as the information each set
requires.
General
The error severity criterion is associated with events in general.
Table 24. Categories of events for IBM Systems Director and event severity
Categories of
events Available settings
Common Agent You can filter these events by selecting one or more the following criteria:
status v Offline
v Online
Update You can filter these events by selecting one or more of the following
manager criteria:
v Installation staging of updates failed
v Installation successful
v Installation failed
v Uninstall successful
v Uninstall failed
v Acquire updates failed
v New updates found
v Check for updates failed
v Compliance failed
Error severity You can filter events by their severity. Select one or more of the following
criteria to create this filter:
v Fatal
v Critical
v Minor
v Warning
v Informational
v Unknown

Hardware
These categories of events are generated by the following hardware and
hardware components: processors (CPUs), disks, fans, memory, network
and switches, power supplies, security, servers, RAID or storage arrays,
and blade servers. None of these categories provide additional settings.
Monitors
These events are generated by the monitors for microprocessor use,
memory use, and disk use. When you select one of these categories of
events, you must set the threshold values for the monitors. Then, a
threshold monitor is automatically created on the specified systems for
you. For more information, see “Managing monitors” and “Managing
thresholds.” The available monitors can vary depending on the selected
target systems. Different target systems might support different
monitors. If you selected multiple target systems, the monitors that are
displayed for selection are those that are supported by at least one of
the selected target systems.

366 IBMSystems Director Systems Management Guide

Table 25. Categories of monitor events and available threshold settings
Categories of
events Available threshold settings
Processor use If you want the monitor to generate a critical event, select the Critical
check box. Then, select the percentage of processor use for the threshold.
When processor use is equal to or greater than the threshold setting, the
monitor will generate a Processor Use event with a critical severity.

If you want the monitor to generate a warning event, select the Warning
check box. Then, select the percentage of processor use for the threshold.
When processor use is equal to or greater than the threshold setting, the
monitor will generate a Processor Use event with a warning severity.
Note: You can set a threshold for both critical and warning events.
Memory use If you want the monitor to generate a critical event, select the Critical
check box. Then, select the amount of memory, in MB, to monitor for the
threshold. When the memory use is equal to or greater than the
threshold settings, the monitor will generate a Memory Use event with a
critical severity.

If you want the monitor to generate a warning event, select the Warning
check box. Then, select the amount of memory, in MB, to monitor for the
threshold. When the memory use is equal to or greater than the
threshold settings, the monitor will generate a Memory Use event with a
warning severity.
Note: You can set a threshold for both critical and warning events.
Disk use If you want the monitor to generate a critical event, select the Critical
check box. Then, select the percentage of disk capacity for the threshold.
When the used disk capacity is equal to or greater than the threshold
setting, the monitor will generate a Disk Use event with a critical
severity.

If you want the monitor to generate a warning event, select the Warning
check box. Then, select the percentage of disk capacity for the threshold.
When the used disk capacity is equal to or greater than the threshold
setting, the monitor will generate a Disk Use event with a warning
severity.
Note: You can set a threshold for both critical and warning events.

Active Energy Monitors

If you have the Active Energy Manager plug-in installed, events that
are generated by Active Energy Manager monitors are available. The
available monitors can vary depending on the selected target systems.
Different target systems might support different Active Energy Manager
monitors. If you selected multiple target systems, the monitors that are
displayed for selection are those that are supported by at least one of
the selected target systems. When you select one of these categories of
events, you must set the threshold values for the monitors. Then, a
threshold monitor is automatically created on the specified systems for
you. For more information, see the IBM Systems Director Active Energy
Manager information center.

Chapter 6. Automating tasks 367

 Table 26. Categories of Active Energy Manager monitor events and available threshold
settings
Categories of
events Available threshold settings
Ambient If you want the monitor to generate a critical event, select the Critical
Temperature check box. Then, select the temperature, in degrees Celsius, to monitor
for the threshold. When the temperature is equal to or greater than the
threshold settings, the monitor will generate an Ambient Temperature
event with a critical severity.

If you want the monitor to generate a warning event, select the Warning
check box. Then, select the temperature, in degrees Celsius, to monitor
for the threshold. When the temperature is equal to or greater than the
threshold settings, the monitor will generate an Ambient Temperature
event with a warning severity.
Note: You can set a threshold for both critical and warning events.
Ambient If you want the monitor to generate a critical event, select the Critical
Temperature check box. Then, select the temperature, in degrees Celsius, to monitor
(externally for the threshold. When the temperature is equal to or greater than the
metered) threshold settings, the monitor will generate an Ambient Temperature
(externally metered) event with a critical severity.

If you want the monitor to generate a warning event, select the Warning
check box. Then, select the temperature, in degrees Celsius, to monitor
for the threshold. When the temperature is equal to or greater than the
threshold settings, the monitor will generate an Ambient Temperature
(externally metered) event with a warning severity.
Note: You can set a threshold for both critical and warning events.
Current If you want the monitor to generate a critical event, select the Critical
check box. Then, select the amperage capacity to monitor for the
threshold. When the current is equal to or greater than the threshold
settings, the monitor will generate a Current event with a critical severity.

If you want the monitor to generate a warning event, select the Warning
check box. Then, select the amperage capacity to monitor for the
threshold. When the current is equal to or greater than the threshold
settings, the monitor will generate a Current event with a warning
severity.
Note: You can set a threshold for both critical and warning events.
Amperage If you want the monitor to generate a critical event, select the Critical
Capacity check box. Then, select the amperage capacity to monitor for the
threshold. When the amperage capacity is equal to or greater than the
threshold settings, the monitor will generate a Amperage Capacity event
with a critical severity.

If you want the monitor to generate a warning event, select the Warning
check box. Then, select the amperage capacity to monitor for the
threshold. When the amperage capacity is equal to or greater than the
threshold settings, the monitor will generate a Amperage Capacity event
with a warning severity.
Note: You can set a threshold for both critical and warning events.

368 IBMSystems Director Systems Management Guide

Table 26. Categories of Active Energy Manager monitor events and available threshold
settings (continued)
Categories of
events Available threshold settings
Average Input If you want the monitor to generate a critical event, select the Critical
Power check box. Then, select the watts for the threshold. When the watts is
equal to or greater than the threshold setting, the monitor will generate
an Average Input Power event with a critical severity.

If you want the monitor to generate a warning event, select the Warning
check box. Then, select the watts for the threshold. When the watts is
equal to or greater than the threshold setting, the monitor will generate a
Average Input Power event with a warning severity.
Note: You can set a threshold for both critical and warning events.
Average Input If you want the monitor to generate a critical event, select the Critical
Power (AC) check box. Then, select the watts for the threshold. When the watts is
equal to or greater than the threshold setting, the monitor will generate
an Average Input Power (AC) event with a critical severity.

If you want the monitor to generate a warning event, select the Warning
check box. Then, select the watts for the threshold. When the watts is
equal to or greater than the threshold setting, the monitor will generate a
Average Input Power (AC) event with a warning severity.
Note: You can set a threshold for both critical and warning events.
Average Input If you want the monitor to generate a critical event, select the Critical
Power (DC) check box. Then, select the watts for the threshold. When the watts is
equal to or greater than the threshold setting, the monitor will generate
an Average Input Power (DC) event with a critical severity.

If you want the monitor to generate a warning event, select the Warning
check box. Then, select the watts for the threshold. When the watts is
equal to or greater than the threshold setting, the monitor will generate a
Average Input Power (DC) event with a warning severity.
Note: You can set a threshold for both critical and warning events.
Average Input If you want the monitor to generate a critical event, select the Critical
Power check box. Then, select the watts for the threshold. When the watts is
(externally equal to or greater than the threshold setting, the monitor will generate
metered) an Average Input Power (externally metered) event with a critical
severity.

If you want the monitor to generate a warning event, select the Warning
check box. Then, select the watts for the threshold. When the watts is
equal to or greater than the threshold setting, the monitor will generate a
Average Input Power (externally metered) event with a warning severity.
Note: You can set a threshold for both critical and warning events.
Average Output If you want the monitor to generate a critical event, select the Critical
Power check box. Then, select the watts for the threshold. When the watts is
equal to or greater than the threshold setting, the monitor will generate
an Average Output Power event with a critical severity.

If you want the monitor to generate a warning event, select the Warning
check box. Then, select the watts for the threshold. When the watts is
equal to or greater than the threshold setting, the monitor will generate
an Average Output Power event with a warning severity.
Note: You can set a threshold for both critical and warning events.

Chapter 6. Automating tasks 369

 Table 26. Categories of Active Energy Manager monitor events and available threshold
settings (continued)
Categories of
events Available threshold settings
Average Output If you want the monitor to generate a critical event, select the Critical
Power (AC) check box. Then, select the watts for the threshold. When the watts is
equal to or greater than the threshold setting, the monitor will generate
an Average Output Power (AC) event with a critical severity.

If you want the monitor to generate a warning event, select the Warning
check box. Then, select the watts for the threshold. When the watts is
equal to or greater than the threshold setting, the monitor will generate
an Average Output Power (AC) event with a warning severity.
Note: You can set a threshold for both critical and warning events.
Average Output If you want the monitor to generate a critical event, select the Critical
Power (DC) check box. Then, select the watts for the threshold. When the watts is
equal to or greater than the threshold setting, the monitor will generate
an Average Output Power (DC) event with a critical severity.

If you want the monitor to generate a warning event, select the Warning
check box. Then, select the watts for the threshold. When the watts is
equal to or greater than the threshold setting, the monitor will generate
an Average Output Power (DC) event with a warning severity.
Note: You can set a threshold for both critical and warning events.
Effective CPU If you want the monitor to generate a critical event, select the Critical
Speed check box. Then, select the speed of effective processor use for the
threshold. When the effective processor use is equal to or greater than
the threshold setting, the monitor will generate an Effective CPU Speed
event with a critical severity.

If you want the monitor to generate a warning event, select the Warning
check box. Then, select the speed of effective processor use for the
threshold. When the effective processor use is equal to or greater than
the threshold setting, the monitor will generate an Effective CPU Speed
event with a warning severity.
Note: You can set a threshold for both critical and warning events.
Exhaust If you want the monitor to generate a critical event, select the Critical
Temperature check box. Then, select the temperature, in degrees Celsius, to monitor
for the threshold. When the temperature is equal to or greater than the
threshold settings, the monitor will generate an Exhaust Temperature
event with a critical severity.

If you want the monitor to generate a warning event, select the Warning
check box. Then, select the temperature, in degrees Celsius, to monitor
for the threshold. When the temperature is equal to or greater than the
threshold settings, the monitor will generate an Exhaust Temperature
event with a warning severity.
Note: You can set a threshold for both critical and warning events.

370 IBMSystems Director Systems Management Guide

Table 26. Categories of Active Energy Manager monitor events and available threshold
settings (continued)
Categories of
events Available threshold settings
Humidity If you want the monitor to generate a critical event, select the Critical
check box. Then, select the percentage of humidity to monitor for the
threshold. When the humidity is equal to or greater than the threshold
settings, the monitor will generate a Humidity (percentage) event with a
critical severity.

If you want the monitor to generate a warning event, select the Warning
check box. Then, select the percentage of humidity to monitor for the
threshold. When the humidity is equal to or greater than the threshold
settings, the monitor will generate a Humidity (percentage) event with a
warning severity.
Note: You can set a threshold for both critical and warning events.
Humidity If you want the monitor to generate a critical event, select the Critical
(externally check box. Then, select the percentage of humidity to monitor for the
metered) threshold. When the humidity is equal to or greater than the threshold
settings, the monitor will generate a Humidity (externally metered)
(percentage) event with a critical severity.

If you want the monitor to generate a warning event, select the Warning
check box. Then, select the percentage of humidity to monitor for the
threshold. When the humidity is equal to or greater than the threshold
settings, the monitor will generate a Humidity (externally metered)
(percentage) event with a warning severity.
Note: You can set a threshold for both critical and warning events.

3. When you are satisfied with the specified event filters, click Next.
Related concepts
“Event filters” on page 335
“Events that are available for filtering” on page 336
“Simple event filter” on page 336
Related tasks
“Selecting specific events for filtering”

Selecting specific events for filtering:

You can select the events that you want to filter. When these events occur, your
event automation plan can respond with one or more customized event actions. If
you want to monitor specific events that are not included in the common event
filters, then you must select advanced event filters. Not only can you specify
additional events, but you also can create more sophisticated event filters that are
triggered when duplicates of an event are received, when a specific number of
instances of an event is received over a range of time, or when a specific event is
received but you want to exclude another event. For information about event filter
types, see “Event filters.” For information about quickly creating common event
filters, see “Selecting common categories of events for filtering.”

Note: This task requires the IBM Systems Director Launched Tasks program. This
program is installed automatically the first time you use a task that requires it. For
information about the IBM Systems Director Launched Tasks program, see
“Starting the IBM Systems Director Launched Tasks program.”

Chapter 6. Automating tasks 371

 To select specific events for filtering in your event automation plan, complete the
following steps:
1. On the Events page, select Advanced event filters from the Events list.
2. Click Create to create a new event filter.

Note: You can select an existing event filter from the table for your event
automation plan. If you want to edit the filter, continue with the following
step. If you want to use the filter without editing it, go to step 18 on page 376.
3. In the Create Filter window, select the filter type that you want to use and
click OK. For information about the filter types, see “Event filters.”
4. In the Event Filter Builder window, clear the Any check box on the Event
Type page.

Note: By default, the Any check box is selected on all pages in the Event
Filter Builder window, indicating that no filtering criteria apply.
5. Expand the Event Type tree and select one or more events for which you want
to filter. You can select more than one event by pressing the Ctrl or Shift key.
The Event Type tree is created dynamically; and entries are added by tasks
and as new events are received. Entries in the tree can be expanded to display
suboption events. Most event filters are created using only this page. It
specifies the source or sources of the events that are to be processed by this
filter.

Note: When you select a root option in the Event Type tree, all suboption
events are selected as well. For example, when you select IBM Systems
Director program in the Event Type tree, all of the collections of events under
IBM Systems Director program are selected also.

If additional event types are published after you create the event filter, the
newly available event types are included in your event filter only if the new
event types are suboption events of an event type that you selected. However,
if you want to include a newly published event type that is not a suboption
event, you must update your event filter by selecting the new event type.
By default, the Any check box is selected, meaning that none of the events
that are listed are filtered, except for Windows-specific and IBM i-specific
events. If you want to specify IBM i-specific events, complete the following
steps:
a. To specify IBM i message queue events, click Include IBM i message
queue events.
b. In the IBM i.Message Queue field, type the message queue event for
which you want to monitor and click Add. The event is displayed in the
list box below. If you want to remove an event, select it and click Delete.

Note: An IBM i message queue event has the following format:

OS/400.msgq.library/message_queue.messageID

where
v library is the library for the event monitor
v message_queue is the message queue for the event monitor
v messageID is the ID of the event monitor
The IBM i.Message Queue field automatically provides the common
message queue event prefix OS/400.msgq. You must type only the unique
portion of the message queue event, for example, QSYS/QSYSOPR.CPF0907.

372 IBMSystems Director Systems Management Guide

 Consider the following examples for monitoring message queue events. In
these examples, the library is QSYS and the message queue is QSYSOPR.
All message IDs that belong to a specific message library and message
queue Type QSYS/QSYSOPR in the IBM i.Message Queue field and click
Add.
A specific message ID that belongs to a specific message library and
queue For example, if the message ID is CPF1234, type
QSYS/QSYSOPR.CPF1234 in the IBM i.Message Queue field and click
Add.
A range of message IDs matching a specific pattern that belong to
specific message library and message queue
For example, to monitor for all message IDs that start with
“CPF12” (all messages from CPF1200 to CPF12FF), type
QSYS/QSYSOPR in the IBM i.Message Queue field and click Add.
Then, click the Event Text tab. On the Event Text page, clear the
Any check box and type the message ID pattern, for example
CPF12, in the Event Text field. Also, make sure Any word is
selected.
6. Optional: To filter events by their event severity, click the Severity tab.
a. Clear the Any check box to select one or more event severities.
b. Select one or more event severity. You can select multiple levels of severity
as filtering criteria. The logical OR operator applies for multiple selections.
For example, if you select Fatal and Critical, the filtering criteria matches
if the originator of the event classifies the event as Fatal or as Critical.
When selecting event severities, consider the following definitions:
Fatal The source of the event has already caused the program to fail and
should be resolved before the program is restarted.
Critical
The source of the event might cause program failure and should
be resolved immediately.
Minor The source of the event should not cause immediate program
failure, but should 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.
7. Optional: To filter events by a specified time range, click the Day and Time
tab. The time zone that applies to this filtering criteria is the time zone in
which the server running IBM Systems Director Server is located. If your
browser system is not in the same time zone as the management server, the
difference in time zones is displayed above the selections pane. For example,
if the management server is located in New York and your browser system is
located in California, the time zone displayed and used is Eastern Standard
Time (EST). The following information is displayed above the selections pane:
Server Time - Local Time = 3 Hours

Chapter 6. Automating tasks 373

 a. Clear the Any check box to select one or more specific days, start times, or
end times.
b. In the Day of the week list, select the day of the week to which this filter
is to apply. Weekday (Monday - Friday) and weekend (Saturday &
Sunday) selections are available.
c. In the Starting time list, select the starting time of an interval within
which this filter is active.
d. In the Ending time list, select the ending time of an interval within which
this filter is active.
e. Click Add to add this time range to the selections pane. You can add
multiple day and time entries to the list.
f. Optional: If you do not want to filter events that were queued for
transmission to IBM Systems Director Server, select Block queued events.
Common Agent can queue events for transmission to IBM Systems Director
Server if the link between the system and the management server was
unavailable. However, you can prevent these queued events from being
processed by the filter by selecting Block queued events. This option can
be useful if the timing of the event is important, or if you want to avoid
filtering on multiple queued events that are sent all at once when IBM
Systems Director Server becomes accessible.
8. Optional: To filter events by their resolution status, click the Category tab.

Note: Not all events have resolutions. To determine if an event provides a

resolution, see the documentation for the specific event in the IBM Systems
Director Events Reference.
a. Clear the Any check box.
b. Select an event category.
9. Optional: To filter events by the source that generated them, click the Sender
Name tab.
Because IBM Systems Director Server keeps track of all systems from which it
has received an event, a list of known sender names (IP addresses or host
names) is provided. The list is dynamic. Initially, only the management server
is displayed in the list. At the time of installation, the management server is
the only system that has registered an event. As other systems generate
events, this list grows. You can enter other IP addresses or host names as
needed. Specifying or selecting sender names can be useful for identifying the
following items:
v The source of SNMP traps
v Systems from which events originate using criteria specified in the genevent
utility
v Systems configured with hardware acquired from another vendor that
generate and forward events
a. Clear the Any check box.
b. Select a system from the list. If a system is not in the list, type the IP
address or host name of the system.
c. Click Add to add the system to the selections pane. You can add multiple
systems.
10. Optional: To filter events by their attributes, click the Extended Attributes tab.
Extended attributes can be particularly useful for narrowing the filtering
criteria to a lower level of detail, for example, to isolate one or more values
originating from a specific system.

374 IBMSystems Director Systems Management Guide

 You cannot specify keywords and values on the Extended Attributes page in
the following situations:
v If you have selected multiple event types or if the Any check box is selected
on the Event Type page, the Extended Attributes page is disabled. You must
select only one event type to specify extended attributes.
v If the Extended Attributes page is enabled for a specific event type but no
keywords are listed, IBM Systems Director Server is not aware of any
keywords that can be used for filtering.
When you specify extended attributes for filtering, an event must meet the
following filtering criteria:
v If you select multiple keywords, all values received must match all values
of all selected keywords (Boolean AND).
v If you specify multiple values for a single keyword, the values received
must match at least one of the values specified for the keyword (Boolean
OR).
Because event types are hierarchical, an event has its extended attributes as
well as the extended attributes of its parent event types. For example, the
event type Director>Topology>Offline has extended attributes for
Director>Topology>Offline and Director>Topology.

Note: To determine what extended attributes an event provides, see the

documentation for that specific event in “Events.”
a. Clear the Any check box.
b. Select an extended attribute from the Keywords list.
c. Select an Boolean operator from the Operator list.
d. Select a value from the Values list.
e. Click Add to add the extended attribute to the selections pane. You can
select additional keyword-value pairs. You also can specify additional
values for a single keyword.
If you want to enter multiple values for a single keyword, click Add each
time you want to add a value. The Boolean OR operator is used to
determine whether an event’s extended attributes meet the filtering criteria
for multiple values of a single keyword. If you enter more than one
keyword and value pair, the Boolean AND operator is used to determine
whether an event’s extended attributes meet the filtering criteria, that is,
all keyword values must be true.
11. Optional: To filter events by their event text, click the Event Text tab.
a. Clear the Any check box to filter selected events based on text in the event.
b. Type the word or words for which you want to filter.
c. Select how you want the word or words to be evaluated. You can select
Any word, All words, or Exact phrase.
d. Optional: If you want the evaluation to be case sensitive, select Case
sensitive.
12. If you have created an event filter using the exclusion event filter type, click
the Excluded Event Type tab to specify the events to exclude.
a. Clear the None check box.
b. Select one or more event types from the tree that you want to exclude
from your filter. Also, you can specify IBM i-specific events to exclude by
clicking the Exclude IBM i message queue events check box and using
the IBM i message queue events pane as described in step 5 on page 372.

Chapter 6. Automating tasks 375

 13. If you have created an event filter using the threshold event filter type, click
the Frequency tab.
For threshold event filters, the Interval field must be used in conjunction with
the Count field. Interval specifies a window of time that begins when an
event meets the filtering criteria. The first occurrence of an event that meets
the criteria does not trigger associated actions, but starts a countdown of the
units that define the interval. For example, if you enter 10 and select minutes,
a 10-minute timer starts when an event meets the filtering criteria. The value
entered in Count specifies the number of times an event must meet the
criteria before associated actions are triggered. For example, if you set Count
to 9, the first 8 events matching the criteria that occur within the interval do
not cause associated actions to trigger. The ninth time an event meets the
criteria within the interval, associated actions are triggered, the count is reset,
and the interval is reset.
a. In the Interval field, specify a window of time that begins when an event
first meets the filtering criteria.
b. In the Count field, type the number of times an event must meet the
criteria before associated actions are triggered.
14. If you have created an event filter using the duplication event filter type, click
the Frequency tab.
For duplication event filters, the Interval field can be used without using the
Count field (Count = 0). The first occurrence of an event that meets the
criteria triggers associated actions and starts a countdown of the units that
define the interval. For example, if you enter 10 and select seconds, a
10-second timer starts when an event meets the filtering criteria. If Count is
set to 0, all other instances of an event that meets the criteria do not trigger
associated actions during the interval.
If Interval is set to a value greater than 0, and Count is set to a value greater
than 0, after the first occurrence of an event meets the filtering criteria, the
value entered in the Count specifies the number of times an event must meet
the criteria within the interval before associated actions can be triggered again.
For example, if you set Count to 9, an event meeting the criteria must occur
nine times within the interval. When an event meets the criteria for a tenth
time within the interval, associated actions are triggered, the count is reset,
and the interval is reset.
a. In the Interval field, specify a window of time to count down when an
event first meets the filtering criteria.
b. Optional: In the Count field, type the number of times an event must meet
the criteria within the interval before associated actions can be triggered
again.
15. Click File → Save As.
16. In the Save Event Filter window, type a name for the filter. When you are
naming an event filter, the name should indicate the type of events for which
the filter is targeted and any special options that you have configured for the
filter, including the time the filter is active and event severity. For example,
the name of an event filter for critical storage events that occur on a weekend
to reflect that purpose.
17. Click OK to save the filter. The new filter is displayed on the Advanced Event
Filters page.
18. When you are satisfied with the event filter, click Next.

376 IBMSystems Director Systems Management Guide

Related concepts
“Events” on page 334
“Event filters” on page 335
“Events that are available for filtering” on page 336
“Simple event filter” on page 336
“Duplication event filter” on page 338
“Exclusion event filter” on page 339
“Threshold event filter” on page 339
Related tasks
“Selecting common categories of events for filtering” on page 365
Related reference
Events Reference

Creating an event action to activate in an event automation plan

The event automation plan uses event actions to automate one or more tasks when
one or more specified events occur.

In most event automation plans, you will use one or more of the following basic
event actions:
v Send an alphanumeric page (using TAP)
v Send an e-mail (Internet SMTP)
v Send an e-mail to a mobile phone
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
If you want to run more complex actions, then you must select an advanced event
action. For information about event action types, see “Event actions.”

To create an event action, complete the following steps:

1. On the Events actions page, click Create.
2. In the Create Actions window, select an event action. For information about
event action types, see “Event actions.”
3. Click OK.
4. 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.”
5. If you selected a basic event action, you can determine whether your settings
are correct by clicking Test.
6. If you selected a basic event action and you are satisfied with the settings, click
OK to save the event action.
7. If you selected an advanced action, click File → Save As. In the Save Event
Action window, type a name for the action. When you are naming an event
action, the name should indicate the action that will take place. For example, if
the event action involves sending an page, begin the event action name with
Pager; if the event action involves sending a message to a phone, begin the
event action name with Phone. Using such a naming convention ensures that
entries are grouped conveniently on the Event Actions page.

Chapter 6. Automating tasks 377

 8. When you are satisfied with your selected event actions, click Next. 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.
Related concepts
“Event actions” on page 340
“Event-data-substitution variables” on page 391

Specifying the time range for event automation plan activation

When creating an event automation plan, you can specify the time range for the
plan to be active. You will want many plans to be active all the time. However,
you might need other plans to be active at only certain times, such as weekends or
overnight.

Complete the following steps to specify the time range for the event automation
plan activation:
1. On the Time range page, choose the period of time over which you want to
collect the events. You can select All day (24 x 7) to enable the plan to be active
all the time. Or you can select Custom to choose specific days for the plan to
be active.
2. If you selected All day (24 x 7), go to step 6. Otherwise, in the Days list, select
the day for which you want to set the start and end times of the time range.
3. Select the All day check box if you want the 24 hours of the selected week day
monitored. However, if you want to monitor less than the 24 hours of the
selected week day, select the start time of the time range from the Start time
list and the end time of the time range from the End time list.
4. Click Add. The day and time range that you specified is added to the event
automation plan and is displayed at the bottom of the Time range page.
5. If you want to specify additional time ranges, repeat steps 2 through 4 for each
time range that you want to specify. If you want to remove one of the time
ranges you specified, select that range and click Remove.
6. When you are satisfied with the specified time ranges, click Next.
7. On the Summary page, verify the details of the event automation plan. If you
need to make changes, click < Back.
8. When you are done editing the event automation plan, click Finish.

The event automation plan is saved and is displayed on the Event Automation
Plans page.

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. In the IBM Systems Director navigation pane, expand Automation and click
Event Automation Plans.
2. On the Event Automation Plans page, select the event automation plan that you
want to copy.
3. Click Create Like.

378 IBMSystems Director Systems Management Guide

 4. On the Name and description page, type a new descriptive name for the event
automation plan that you are creating. Optionally, you also can type a
description of the plan. Click Next.
5. In the Event Automation Plan wizard, navigate to the pages that you want to
edit and make your changes.
6. On the Summary page, verify the details of the event automation plan. If you
need to make changes, click < Back.
7. When you are done editing the event automation plan, click Finish.

The event automation plan is saved and is displayed on the Event Automation
Plans page.
Related tasks
“Viewing event automation plans associated with a resource” on page 363
“Creating an event automation plan” on page 364
“Editing an event automation plan”
“Deactivating and activating an event automation plan” on page 380
“Viewing event automation plan properties” on page 381
“Deleting an event automation plan” on page 381
Related reference
mkevtautopln 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:

1. In the IBM Systems Director navigation pane, expand Automation and click
Event Automation Plans.
2. On the Event Automation Plans page, select the event automation plan that you
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.
5. On the Summary page, verify the details of the event automation plan. If you
need to make changes, click < Back.
6. When you are done editing the event automation plan, click Finish.

The event automation plan is saved and is displayed on the Event Automation
Plans page.

Chapter 6. Automating tasks 379

 Related tasks
“Viewing event automation plans associated with a resource” on page 363
“Creating an event automation plan” on page 364
“Copying an event automation plan” on page 378
“Deactivating and activating an event automation plan”
“Viewing event automation plan properties” on page 381
“Deleting an event automation plan” on page 381
Related reference
chevtautopln command
evtautopln command

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:
1. In the IBM Systems Director navigation pane, expand Automation and click
Event Automation Plans.
2. On the Event Automation Plans page, select the event automation plan that you
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.

380 IBMSystems Director Systems Management Guide

 Related tasks
“Viewing event automation plans associated with a resource” on page 363
“Creating an event automation plan” on page 364
“Copying an event automation plan” on page 378
“Editing an event automation plan” on page 379
“Viewing event automation plan properties”
“Deleting an event automation plan”
Related reference
evtautopln command

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:

1. In the IBM Systems Director navigation pane, expand Automation and click
Event Automation Plans.
2. On the Event Automation Plans page, select the event automation plan whose
properties you want to view.
3. Click Actions → Properties.
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 tasks
“Viewing event automation plans associated with a resource” on page 363
“Creating an event automation plan” on page 364
“Copying an event automation plan” on page 378
“Editing an event automation plan” on page 379
“Deactivating and activating an event automation plan” on page 380
“Deleting an event automation plan”
Related reference
lsevtautopln 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:

1. In the IBM Systems Director navigation pane, expand Automation and click
Event Automation Plans.
2. On the Event Automation Plans page, select the event automation plan that you
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.

Chapter 6. Automating tasks 381

 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 tasks
“Viewing event automation plans associated with a resource” on page 363
“Creating an event automation plan” on page 364
“Copying an event automation plan” on page 378
“Editing an event automation plan” on page 379
“Deactivating and activating an event automation plan” on page 380
“Viewing event automation plan properties” on page 381
Related reference
rmevtautopln 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 an event action’s
history.
Related reference
Viewing event actions (lsevtact command)
Generating events for testing purposes (genevent 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.

Note: This task requires the IBM Systems Director Launched Tasks program. This
program is installed automatically the first time you use a task that requires it. For
information about the IBM Systems Director Launched Tasks program, see
“Starting the IBM Systems Director Launched Tasks program.”

To create an event action, complete the following steps:

1. In the IBM Systems Director navigation area, expand Automation and click
Event Actions.
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. 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.”
6. If you selected a basic event action, you can determine whether your settings
are correct by clicking Test.

382 IBMSystems Director Systems Management Guide

 7. If you selected a basic event action and you are satisfied with the settings, click
OK to save the event action.
8. If you selected an advanced action, click File → Save As. In the Save Event
Action window, type a name for the action. When you are naming an event
action, the name should indicate the action that will take place. For example, if
the event action involves sending an page, begin the event action name with
Pager; if the event action involves sending a message to a phone, begin the
event action name with Phone. Using such a naming convention ensures that
entries are grouped conveniently on the Event Actions page.

The event action is saved and is displayed on the Event Actions page.
Related concepts
“Event actions” on page 340
“Event-data-substitution variables” on page 391
Related tasks
“Editing an event action”
“Copying an event action” on page 384
“Testing an event action” on page 385
“Deleting an event action” on page 386
“Activating and deactivating an event-action history” on page 387
“Viewing an event-action history” on page 388
“Refreshing an event-action-history log entries” on page 390
“Deleting event-action-history log entries” on page 390
“Viewing event action properties” on page 390
Related reference
mkevtactemail command
mkevtactstpgm command
mkevtactsttask command

Editing an event action

Edit an event action to change settings in a preexisting event action.

Note: This task requires the IBM Systems Director Launched Tasks program. This
program is installed automatically the first time you use a task that requires it. For
information about the IBM Systems Director Launched Tasks program, see
“Starting the IBM Systems Director Launched Tasks program.”

To edit an event action, complete the following steps:

1. In the IBM Systems Director navigation area, expand Automation and click
Event Actions.
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.
5. If you selected a basic event action, you can determine whether your settings
are correct by clicking Test.
6. If you selected a basic event action and you are satisfied with the settings, click
OK to save the event action.
7. If you selected an advanced action, click File → Save.

Chapter 6. Automating tasks 383

 The event action is saved and is displayed on the Event Actions page.
Related concepts
“Event-data-substitution variables” on page 391
Related tasks
“Creating an event action” on page 382
“Copying an event action”
“Testing an event action” on page 385
“Deleting an event action” on page 386
“Activating and deactivating an event-action history” on page 387
“Viewing an event-action history” on page 388
“Refreshing an event-action-history log entries” on page 390
“Deleting event-action-history log entries” on page 390
“Viewing event action properties” on page 390

Copying an event action

Copy an event action when you want to create an event action that is similar to a
preexisting event action.

Note: This task requires the IBM Systems Director Launched Tasks program. This
program is installed automatically the first time you use a task that requires it. For
information about the IBM Systems Director Launched Tasks program, see
“Starting the IBM Systems Director Launched Tasks program.”

To copy an event action, complete the following steps:

1. In the IBM Systems Director navigation area, expand Automation and click
Event Actions.
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.
5. If you selected a basic event action, you can determine whether your settings
are correct by clicking Test.
6. If you selected a basic event action and you are satisfied with the settings, click
OK to save the event action.
7. If you selected an advanced action, click File → Save As. In the Save Event
Action window, type a name for the action. When you are naming an event
action, the name should indicate the action that will take place. For example, if
the event action involves sending an page, begin the event action name with
Pager; if the event action involves sending a message to a phone, begin the
event action name with Phone. Using such a naming convention ensures that
entries are grouped conveniently on the Event Actions page.

The event action is saved and is displayed on the Event Actions page.

384 IBMSystems Director Systems Management Guide

 Related concepts
“Event-data-substitution variables” on page 391
Related tasks
“Creating an event action” on page 382
“Editing an event action” on page 383
“Testing an event action”
“Deleting an event action” on page 386
“Activating and deactivating an event-action history” on page 387
“Viewing an event-action history” on page 388
“Refreshing an event-action-history log entries” on page 390
“Deleting event-action-history log entries” on page 390
“Viewing event action properties” on page 390
Related reference
mkevtactemail command
mkevtactstpgm command
mkevtactsttask command

Testing an event action

You can test an event action to make sure the settings you have chosen 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:

1. In the IBM Systems Director navigation area, expand Automation and click
Event Actions.
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 tested 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.
6. On the Properties page, click the History tab to view details about the test.

Chapter 6. Automating tasks 385

 Related concepts
“Send an alphanumeric page (using TAP)” on page 340
“Send an e-mail to a mobile phone” on page 342
“Send an e-mail (Internet SMTP) ” on page 341
“Start a program on a system” on page 343
“Start a program on the management server” on page 345
“Start a task on a specified system” on page 355
“Event-data-substitution variables” on page 391
Related tasks
“Creating an event action” on page 382
“Editing an event action” on page 383
“Copying an event action” on page 384
“Deleting an event action”
“Activating and deactivating an event-action history” on page 387
“Viewing an event-action history” on page 388
“Refreshing an event-action-history log entries” on page 390
“Deleting event-action-history log entries” on page 390
“Viewing event action properties” on page 390
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:

1. In the IBM Systems Director navigation area, expand Automation and click
Event Actions.
2. On the Event Actions page, select the event action that you want to delete.

Note: You can delete more than one event action at a time.
3. Click Delete.
4. In the confirmation window, 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.

386 IBMSystems Director Systems Management Guide

 Related tasks
“Creating an event action” on page 382
“Editing an event action” on page 383
“Copying an event action” on page 384
“Testing an event action” on page 385
“Activating and deactivating an event-action history”
“Viewing an event-action history” on page 388
“Refreshing an event-action-history log entries” on page 390
“Deleting event-action-history log entries” on page 390
“Viewing event action properties” on page 390
Related reference
rmevtact command

Activating and deactivating an event-action history

You can start the recording of when an event action is invoked by activating the
event-action history. When you want the history to stop recording, you can
subsequently deactivate the event-action history. By default, event-action history is
deactivated. To view an event-action history, see “Viewing an event-action history.”

Recording an event action’s history can provide useful information. For example,
you can create an event automation plan that includes an event action that runs a
program to cleanup temporary files in order to reduce disk-space use. When you
activate this event-action history, the following information is recorded:
v The date and time when the event action was run and, subsequently, the
cleanup program was run
v Whether the program was run successfully
v The event that triggered the event automation plan

To start and then stop the recording of an event-action history, complete the
following steps:
1. In the IBM Systems Director navigation area, expand Automation and click
Event Actions.
2. On the Event Actions page, select the event action with the history that you
want to start recording.

Note: You can activate recording the history for more than one event action at
a time.
3. Click Actions → Activate History. The recording of the event-action history is
activated. On the Event Actions page in the History column, the value is
changed from Inactive to Active. A message is displayed on the page stating
that recording of the event-action history was activated successfully.
4. When you want to stop the recording of an event-action history, select the
event action and click Actions → Deactivate History. The recording of the
event-action history is deactivated. On the Event Actions page in the History
column, the value is changed from Active to Inactive. A message is displayed
on the page stating that recording of the event-action history was deactivated
successfully.

Chapter 6. Automating tasks 387

 Related tasks
“Creating an event action” on page 382
“Editing an event action” on page 383
“Copying an event action” on page 384
“Testing an event action” on page 385
“Deleting an event action” on page 386
“Viewing an event-action history”
“Refreshing an event-action-history log entries” on page 390
“Deleting event-action-history log entries” on page 390
“Viewing event action properties” on page 390
Related reference
evtacthist command

Viewing an event-action history

You can view an event-action history for information about how an event action
has run in your systems-management environment.

Before an event-action history can be recorded, you must activate the event-action
history. For information, see “Activating and deactivating an event-action history.”

Recording an event action’s history can provide useful information. For example,
you can create an event automation plan that includes an event action that runs a
program to cleanup temporary files in order to reduce disk-space use. When you
activate this event-action history, the following information is recorded:
v The date and time when the event action was run and, subsequently, the
cleanup program was run
v Whether the program was run successfully
v The event that triggered the event automation plan

To view an event-action history, complete the following steps:

1. In the IBM Systems Director navigation area, expand Automation and click
Event Actions.
2. On the Event Actions page, select the event action whose history you want to
view.
3. Click Actions → Properties.
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 is
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 is
run successfully. Possible values are successful, failed, and not
performed.

388 IBMSystems Director Systems Management Guide

 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 resent 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 has occurred.
Resolution
A problem has been resolved and is no longer a problem.
Event Severity
The severity level of the event, which identifies potentially urgent
problems requiring immediate attention. Possible severities are:
Fatal The source of the event has already caused the program to fail
and should be resolved before the program is restarted.
Critical
The source of the event might cause program failure and
should be resolved immediately.
Minor The source of the event should not cause immediate program
failure, but should 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
usually contains the name of the management server.

Chapter 6. Automating tasks 389

 Related tasks
“Creating an event action” on page 382
“Editing an event action” on page 383
“Copying an event action” on page 384
“Testing an event action” on page 385
“Deleting an event action” on page 386
“Activating and deactivating an event-action history” on page 387
“Refreshing an event-action-history log entries”
“Deleting event-action-history log entries”
“Viewing event action properties”
Related reference
lsevtacthist command

Refreshing an event-action-history log entries

You can refresh event-action-history log entries to view the latest available entries.

To refresh log entries, complete the following steps:

1. In the IBM Systems Director navigation area, expand Automation and click
Event Actions.
2. On the Event Actions page, select the event action whose history you want to
view.
3. Click Actions → Properties.
4. On the Properties page, click the History tab to view the event-action history.
5. On the History page, click Refresh. The list of available log entries is refreshed.

Deleting event-action-history log entries

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:

1. In the IBM Systems Director navigation area, expand Automation and click
Event Actions.
2. On the Event Actions page, select the event action whose history-log entries
you want to delete.
3. Click Actions → Properties.
4. On the Properties page, click the History tab to view the event-action history.
5. Select one or more log entries that you want to delete.
6. Click Delete.
7. In the confirmation window, 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.

390 IBMSystems Director Systems Management Guide

 To view event-action properties, complete the following steps:
1. In the IBM Systems Director navigation area, expand Automation and click
Event Actions.
2. On the Event Actions page, select the event action whose properties you want
to view.
3. Click Actions → Properties.
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
because there are none available on the Properties page.
Related tasks
“Creating an event action” on page 382
“Editing an event action” on page 383
“Copying an event action” on page 384
“Testing an event action” on page 385
“Deleting an event action” on page 386
“Activating and deactivating an event-action history” on page 387
“Viewing an event-action history” on page 388
“Refreshing an event-action-history log entries” on page 390
“Deleting event-action-history log entries” on page 390
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
&time The localized time at which the event occurred.

Chapter 6. Automating tasks 391

 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 IP address or host name of the system on which the event was
generated. The system name is either the name of the system running
Common Agent or, in the case of 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.

392 IBMSystems Director Systems Management Guide

 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

Chapter 6. Automating tasks 393

 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 346
“Modify an event and send it” on page 347
“Post to a newsgroup (NNTP)” on page 348
“Send an alphanumeric page (using TAP)” on page 340
“Send an e-mail to a mobile phone” on page 342
“Send an e-mail (Internet SMTP) ” on page 341
“Set an event system variable” on page 354
“Static group: add or remove group members” on page 357
“Static group: add or remove the event-generating system” on page 358
“Timed alarm that generates an event” on page 359
“Timed alarm that starts a program” on page 360
Related tasks
“Creating an event action” on page 382
“Editing an event action” on page 383
“Copying an event action” on page 384
“Testing an event action” on page 385
“Deleting an event action” on page 386
“Activating and deactivating an event-action history” on page 387
“Viewing an event-action history” on page 388
“Refreshing an event-action-history log entries” on page 390
“Deleting event-action-history log entries” on page 390
“Viewing event action properties” on page 390

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.

394 IBMSystems Director Systems Management Guide

 Related reference
Viewing event types (lsevttype command)
Generating events for testing purposes (genevent command)

Creating an event filter

Create an event filter to use in your event automation plans. You can create event
filters before using them in your event automation plans. Typically, you create
event filters in the Event Automation Plan wizard. However, there might be times
when you want to create an event filter that you can use in event automation plans
at another time.

Note: This task requires the IBM Systems Director Launched Tasks program. This
program is installed automatically the first time you use a task that requires it. For
information about the IBM Systems Director Launched Tasks program, see
“Starting the IBM Systems Director Launched Tasks program.”

To create an event filter, complete the following steps:

1. In the IBM Systems Director navigation pane, expand Automation and click
Event Filters.
2. Click Create.
3. In the Create Filter window, select the filter type that you want to use and
click OK. For information about the filter types, see “Event filters.”
4. In the Event Filter Builder window, clear the Any check box on the Event
Type page.

Note: By default, the Any check box is selected on all pages in the Event
Filter Builder window, indicating that no filtering criteria apply.
5. Expand the Event Type tree and select one or more events for which you want
to filter. You can select more than one event by pressing the Ctrl or Shift key.
The Event Type tree is created dynamically; and entries are added by tasks
and as new events are received. Entries in the tree can be expanded to display
suboption events. Most event filters are created using only this page. It
specifies the source or sources of the events that are to be processed by this
filter.

Note: When you select a root option in the Event Type tree, all suboption
events are selected as well. For example, when you select IBM Systems
Director program in the Event Type tree, all of the collections of events under
IBM Systems Director program are selected also.

If additional event types are published after you create the event filter, the
newly available event types are included in your event filter only if the new
event types are suboption events of an event type that you selected. However,
if you want to include a newly published event type that is not a suboption
event, you must update your event filter by selecting the new event type.
By default, the Any check box is selected, meaning that none of the events
that are listed are filtered, except for Windows-specific and IBM i-specific
events. If you want to specify IBM i-specific events, complete the following
steps:
a. To specify IBM i message queue events, click Include IBM i message
queue events.

Chapter 6. Automating tasks 395

 b. In the IBM i.Message Queue field, type the message queue event for
which you want to monitor and click Add. The event is displayed in the
list box below. If you want to remove an event, select it and click Delete.

Note: An IBM i message queue event has the following format:

OS/400.msgq.library/message_queue.messageID

where
v library is the library for the event monitor
v message_queue is the message queue for the event monitor
v messageID is the ID of the event monitor
The IBM i.Message Queue field automatically provides the common
message queue event prefix OS/400.msgq. You must type only the unique
portion of the message queue event, for example, QSYS/QSYSOPR.CPF0907.
Consider the following examples for monitoring message queue events. In
these examples, the library is QSYS and the message queue is QSYSOPR.
All message IDs that belong to a specific message library and message
queue Type QSYS/QSYSOPR in the IBM i.Message Queue field and click
Add.
A specific message ID that belongs to a specific message library and
queue For example, if the message ID is CPF1234, type
QSYS/QSYSOPR.CPF1234 in the IBM i.Message Queue field and click
Add.
A range of message IDs matching a specific pattern that belong to
specific message library and message queue
For example, to monitor for all message IDs that start with
“CPF12” (all messages from CPF1200 to CPF12FF), type
QSYS/QSYSOPR in the IBM i.Message Queue field and click Add.
Then, click the Event Text tab. On the Event Text page, clear the
Any check box and type the message ID pattern, for example
CPF12, in the Event Text field. Also, make sure Any word is
selected.
6. Optional: To filter events by their event severity, click the Severity tab.
a. Clear the Any check box to select one or more event severities.
b. Select one or more event severity. You can select multiple levels of severity
as filtering criteria. The logical OR operator applies for multiple selections.
For example, if you select Fatal and Critical, the filtering criteria matches
if the originator of the event classifies the event as Fatal or as Critical.
When selecting event severities, consider the following definitions:
Fatal The source of the event has already caused the program to fail and
should be resolved before the program is restarted.
Critical
The source of the event might cause program failure and should
be resolved immediately.
Minor The source of the event should not cause immediate program
failure, but should 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

396 IBMSystems Director Systems Management Guide

 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.
7. Optional: To filter events by a specified time range, click the Day and Time
tab. The time zone that applies to this filtering criteria is the time zone in
which the server running IBM Systems Director Server is located. If your
browser system is not in the same time zone as the management server, the
difference in time zones is displayed above the selections pane. For example,
if the management server is located in New York and your browser system is
located in California, the time zone displayed and used is Eastern Standard
Time (EST). The following information is displayed above the selections pane:
Server Time - Local Time = 3 Hours
a. Clear the Any check box to select one or more specific days, start times, or
end times.
b. In the Day of the week list, select the day of the week to which this filter
is to apply. Weekday (Monday - Friday) and weekend (Saturday &
Sunday) selections are available.
c. In the Starting time list, select the starting time of an interval within
which this filter is active.
d. In the Ending time list, select the ending time of an interval within which
this filter is active.
e. Click Add to add this time range to the selections pane. You can add
multiple day and time entries to the list.
f. Optional: If you do not want to filter events that were queued for
transmission to IBM Systems Director Server, select Block queued events.
Common Agent can queue events for transmission to IBM Systems Director
Server if the link between the system and the management server was
unavailable. However, you can prevent these queued events from being
processed by the filter by selecting Block queued events. This option can
be useful if the timing of the event is important, or if you want to avoid
filtering on multiple queued events that are sent all at once when IBM
Systems Director Server becomes accessible.
8. Optional: To filter events by their resolution status, click the Category tab.

Note: Not all events have resolutions. To determine if an event provides a

resolution, see the documentation for the specific event in the IBM Systems
Director Events Reference.
a. Clear the Any check box.
b. Select an event category.
9. Optional: To filter events by the source that generated them, click the Sender
Name tab.
Because IBM Systems Director Server keeps track of all systems from which it
has received an event, a list of known sender names (IP addresses or host
names) is provided. The list is dynamic. Initially, only the management server
is displayed in the list. At the time of installation, the management server is
the only system that has registered an event. As other systems generate
events, this list grows. You can enter other IP addresses or host names as
needed. Specifying or selecting sender names can be useful for identifying the
following items:
v The source of SNMP traps

Chapter 6. Automating tasks 397

 v Systems from which events originate using criteria specified in the genevent
utility
v Systems configured with hardware acquired from another vendor that
generate and forward events
a. Clear the Any check box.
b. Select a system from the list. If a system is not in the list, type the IP
address or host name of the system.
c. Click Add to add the system to the selections pane. You can add multiple
systems.
10. Optional: To filter events by their attributes, click the Extended Attributes tab.
Extended attributes can be particularly useful for narrowing the filtering
criteria to a lower level of detail, for example, to isolate one or more values
originating from a specific system.
You cannot specify keywords and values on the Extended Attributes page in
the following situations:
v If you have selected multiple event types or if the Any check box is selected
on the Event Type page, the Extended Attributes page is disabled. You must
select only one event type to specify extended attributes.
v If the Extended Attributes page is enabled for a specific event type but no
keywords are listed, IBM Systems Director Server is not aware of any
keywords that can be used for filtering.
When you specify extended attributes for filtering, an event must meet the
following filtering criteria:
v If you select multiple keywords, all values received must match all values
of all selected keywords (Boolean AND).
v If you specify multiple values for a single keyword, the values received
must match at least one of the values specified for the keyword (Boolean
OR).
Because event types are hierarchical, an event has its extended attributes as
well as the extended attributes of its parent event types. For example, the
event type Director>Topology>Offline has extended attributes for
Director>Topology>Offline and Director>Topology.

Note: To determine what extended attributes an event provides, see the

documentation for that specific event in “Events.”
a. Clear the Any check box.
b. Select an extended attribute from the Keywords list.
c. Select an Boolean operator from the Operator list.
d. Select a value from the Values list.
e. Click Add to add the extended attribute to the selections pane. You can
select additional keyword-value pairs. You also can specify additional
values for a single keyword.
If you want to enter multiple values for a single keyword, click Add each
time you want to add a value. The Boolean OR operator is used to
determine whether an event’s extended attributes meet the filtering criteria
for multiple values of a single keyword. If you enter more than one
keyword and value pair, the Boolean AND operator is used to determine
whether an event’s extended attributes meet the filtering criteria, that is,
all keyword values must be true.
11. Optional: To filter events by their event text, click the Event Text tab.
a. Clear the Any check box to filter selected events based on text in the event.

398 IBMSystems Director Systems Management Guide

 b. Type the word or words for which you want to filter.
c. Select how you want the word or words to be evaluated. You can select
Any word, All words, or Exact phrase.
d. Optional: If you want the evaluation to be case sensitive, select Case
sensitive.
12. If you have created an event filter using the exclusion event filter type, click
the Excluded Event Type tab to specify the events to exclude.
a. Clear the None check box.
b. Select one or more event types from the tree that you want to exclude
from your filter. Also, you can specify IBM i-specific events to exclude by
clicking the Exclude IBM i message queue events check box and using
the IBM i message queue events pane as described in step 5 on page 372.
13. If you have created an event filter using the threshold event filter type, click
the Frequency tab.
For threshold event filters, the Interval field must be used in conjunction with
the Count field. Interval specifies a window of time that begins when an
event meets the filtering criteria. The first occurrence of an event that meets
the criteria does not trigger associated actions, but starts a countdown of the
units that define the interval. For example, if you enter 10 and select minutes,
a 10-minute timer starts when an event meets the filtering criteria. The value
entered in Count specifies the number of times an event must meet the
criteria before associated actions are triggered. For example, if you set Count
to 9, the first 8 events matching the criteria that occur within the interval do
not cause associated actions to trigger. The ninth time an event meets the
criteria within the interval, associated actions are triggered, the count is reset,
and the interval is reset.
a. In the Interval field, specify a window of time that begins when an event
first meets the filtering criteria.
b. In the Count field, type the number of times an event must meet the
criteria before associated actions are triggered.
14. If you have created an event filter using the duplication event filter type, click
the Frequency tab.
For duplication event filters, the Interval field can be used without using the
Count field (Count = 0). The first occurrence of an event that meets the
criteria triggers associated actions and starts a countdown of the units that
define the interval. For example, if you enter 10 and select seconds, a
10-second timer starts when an event meets the filtering criteria. If Count is
set to 0, all other instances of an event that meets the criteria do not trigger
associated actions during the interval.
If Interval is set to a value greater than 0, and Count is set to a value greater
than 0, after the first occurrence of an event meets the filtering criteria, the
value entered in the Count specifies the number of times an event must meet
the criteria within the interval before associated actions can be triggered again.
For example, if you set Count to 9, an event meeting the criteria must occur
nine times within the interval. When an event meets the criteria for a tenth
time within the interval, associated actions are triggered, the count is reset,
and the interval is reset.
a. In the Interval field, specify a window of time to count down when an
event first meets the filtering criteria.
b. Optional: In the Count field, type the number of times an event must meet
the criteria within the interval before associated actions can be triggered
again.

Chapter 6. Automating tasks 399

 15. Click File → Save As.
16. In the Save Event Filter window, type a name for the filter. When you are
naming an event filter, the name should indicate the type of events for which
the filter is targeted and any special options that you have configured for the
filter, including the time the filter is active and event severity. For example,
the name of an event filter for critical storage events that occur on a weekend
to reflect that purpose.
17. Click OK to save the filter.

The event filter is saved and is displayed in the Event Filters page.
Related concepts
“Events that are available for filtering” on page 336
“Simple event filter” on page 336
“Duplication event filter” on page 338
“Exclusion event filter” on page 339
“Threshold event filter” on page 339
Related tasks
“Viewing the automation manager summary” on page 362
“Editing an event filter”
“Copying an event filter” on page 401
“Viewing event filter properties” on page 402
“Viewing predefined filter criteria” on page 402
“Deleting an event filter” on page 403
Related reference
Events Reference

Editing an event filter

Edit an event filter to change settings in a preexisting event filter.

Note: This task requires the IBM Systems Director Launched Tasks program. This
program is installed automatically the first time you use a task that requires it. For
information about the IBM Systems Director Launched Tasks program, see
“Starting the IBM Systems Director Launched Tasks program.”

To edit an event filter, complete the following steps:

1. In the IBM Systems Director navigation pane, expand Automation and click
Event Filters.
2. On the Event Filters page, select the event filter that you want to edit.
3. Click Edit.
4. In the Event Filter Builder window, complete the applicable fields for the event
filter that you want to edit. For more information about specifying criteria for
an event filter, see “Selecting specific events for filtering.”
5. Click File → Save.
6. Click OK to save the filter.

The event filter is saved and is displayed in the Event Filters page.

400 IBMSystems Director Systems Management Guide

 Related concepts
“Events that are available for filtering” on page 336
“Simple event filter” on page 336
“Duplication event filter” on page 338
“Exclusion event filter” on page 339
“Threshold event filter” on page 339
Related tasks
“Selecting specific events for filtering” on page 371
“Viewing the automation manager summary” on page 362
“Creating an event filter” on page 395
“Copying an event filter”
“Viewing event filter properties” on page 402
“Viewing predefined filter criteria” on page 402
“Deleting an event filter” on page 403

Copying an event filter

Copy an event filter when you want to create an event filter that is similar to a
preexisting event filter.

Note: This task requires the IBM Systems Director Launched Tasks program. This
program is installed automatically the first time you use a task that requires it. For
information about the IBM Systems Director Launched Tasks program, see
“Starting the IBM Systems Director Launched Tasks program.”

To copy an event filter, complete the following steps:

1. In the IBM Systems Director navigation pane, expand Automation and click
Event Filters.
2. On the Event Filters page, select the event filter that you want to copy.
3. Click Create Like. The Event Filter Builder window is displayed.
4. In the Event Filter Builder window, complete the applicable fields for the event
filter that you want to edit. For more information about specifying criteria for
an event filter, see “Selecting specific events for filtering.”
5. Click File → Save.
6. In the Save Event Filter window, type a name for the filter. When you are
naming an event filter, the name should indicate the type of events for which
the filter is targeted and any special options that you have configured for the
filter, including the time the filter is active and event severity. For example, the
name of an event filter for critical storage events that occur on a weekend to
reflect that purpose.
7. Click OK to save the filter.

The event filter is saved and is displayed in the Event Filters page.

Chapter 6. Automating tasks 401

 Related concepts
“Events that are available for filtering” on page 336
“Simple event filter” on page 336
“Duplication event filter” on page 338
“Exclusion event filter” on page 339
“Threshold event filter” on page 339
Related tasks
“Selecting specific events for filtering” on page 371
“Viewing the automation manager summary” on page 362
“Creating an event filter” on page 395
“Editing an event filter” on page 400
“Viewing event filter properties”
“Viewing predefined filter criteria”
“Deleting an event filter” on page 403

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:

1. In the IBM Systems Director navigation pane, expand Automation and click
Event Filters.
2. On the Event Filters page, select the event filter whose properties you want to
view.
3. Click Actions → Properties.
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
because there are none available on the Properties page.
Related tasks
“Viewing the automation manager summary” on page 362
“Creating an event filter” on page 395
“Editing an event filter” on page 400
“Copying an event filter” on page 401
“Viewing predefined filter criteria”
“Deleting an event filter” on page 403
Related reference
lsevtfltr command

Viewing predefined filter criteria

You can view the criteria used to define a predefined event filter.

Note: This task requires the IBM Systems Director Launched Tasks program. This
program is installed automatically the first time you use a task that requires it. For
information about the IBM Systems Director Launched Tasks program, see
“Starting the IBM Systems Director Launched Tasks program.”

402 IBMSystems Director Systems Management Guide

 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:
1. In the IBM Systems Director navigation pane, expand Automation and click
Event Filters.
2. On the Event Filters page, select the predefined filter that you want to view.
3. Click Actions → Properties.
Related concepts
“Simple event filter” on page 336
Related tasks
“Creating an event filter” on page 395
“Editing an event filter” on page 400
“Copying an event filter” on page 401
“Viewing event filter properties” on page 402
“Deleting an event filter”

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:

1. In the IBM Systems Director navigation pane, expand Automation and click
Event Filters.
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.
4. In the confirmation window, 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
“Viewing the automation manager summary” on page 362
“Creating an event filter” on page 395
“Editing an event filter” on page 400
“Copying an event filter” on page 401
“Viewing event filter properties” on page 402
“Viewing predefined filter criteria” on page 402
Related reference
rmevtfltr command

Chapter 6. Automating tasks 403

404 IBMSystems Director Systems Management Guide
Chapter 7. Updating systems
Use the IBM Systems Director update manager plugin to acquire, install, and
manage updates, as well as to monitor your systems to ensure that they remain
current.

See this tutorial in order to become familiar with update manager before using it:
“eLearning: Updating firmware and software”
(publib.boulder.ibm.com/infocenter/systems/topic/director_6.1/
fqm0_c_elearning_updating_firmware_and_software.html)

You can manage individual updates, or sets of updates known as update

collections.

Update manager performs these tasks:

v Manages and installs updates to existing software products and firmware,
external network and storage switches, and external storage servers.
v Installs updates to IBM Systems Director agents that have already been installed.
v For an individual update or update collection, performs this sequence of tasks to
acquire and install it:
1. Download, 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. Installation, which installs an update
4. Uninstall, which removes an update. Not all updates support the uninstall
task.
v Manages Compliance policies, which provide notification of when systems are
in need of updates, and which updates are needed.
v Schedules a check for updates, which is a search for new updates that update
manager is currently not aware of. If any new updates are found, update
manager obtains necessary information to include these updates.
v Provide details about a specific update, such as its documentation and
prerequisite requirements (requisite updates).
v Displays information about updates that were installed by IBM Systems Director.
Updates installed by other means are not displayed.

Update manager does not perform these tasks:

v Install new software products.
v Install IBM Systems Director agents on systems that currently do not have an
agent.
IBM Systems Director agents can be installed with the agent manager plugin of
IBM Systems Director.
v Migrate to IBM Systems Director 6.1 from any other release of IBM Director.
v Migrate to IBM Director 5.2 from IBM Director 5.1.
v Perform actions on systems that are locked. Update actions can be performed
only on systems that are unlocked.

© Copyright IBM Corp. 1999, 2009 405

 If a system is locked, the update menu actions will not be displayed for it. You
cannot select a locked system in any of the system selection actions (System
page in the Install wizard, Installation staging wizard, and so forth).
Inventory collection must be run on any unlocked systems that are to be
monitored for update management and compliance status. Applicability of
updates to a system cannot be determined unless inventory has been collected
on the system.
v Update a different instance of the IBM Systems Director Server.
Related tasks
Installing agents

Supported updates
This is a list of updates and the systems to which they apply. Unless otherwise
noted, the systems can be Common Agent-managed systems, Platform
Agent-managed systems, and Agentless-managed systems.
v IBM Systems Director 6.1
– IBM Systems Director Web interface
– IBM Systems Director Server
– Common Agent
v Level 1 and Level 2 agents of IBM Director V5.20.
v Technology Levels and Service Packs for IBM AIX 5.3 TL6 SP5 and later. (IBM
Systems Director Server or Common Agent only.)
v Technology Levels and Service Packs for IBM AIX 6.1. (IBM Systems Director
Server or Common Agent only.)
v Linux, Novell Distribution
v Cumulative PTF package and PTF Groups for IBM i (formerly i5/OS) systems
running Platform Agent-managed systems.
v Hardware Management Console (HMC) systems with Hardware Management
Console V7.3.3 SP2 and later. All updates will be Hardware Management
Console V7.3.3 and later as well.
v Power Systems Firmware for all IBM Power Systems p5 and later systems that
meet one of these criteria:
– In-band stand alone (not managed by Hardware Management Console) IBM
Power Systems target systems running AIX or Linux. These systems must
have the Common Agent installed.
– Out-of-band (managed by Hardware Management Console) target systems
running IBM i. No Common Agent is required because Secure Shell (SSH)
performs the update.
– IBM Power Systems target systems managed by Integrated Virtualization
Manager and running VIOS version 1.5.0.0 or later. No Common Agent is
required, because SSH performs the update.
v IBM BladeCenter I/O Module Firmware. Inventory for these devices is provided
by SNMP.
v IBM BladeCenter Management Modules, Advanced Management Modules, and
Passthrough Modules. For these devices, inventory is provided by SNMP.
v IBM System x servers running Linux or Windows, device driver and firmware
updates. Support is provided for servers running all agent levels, including IBM
Director V5.2 agents and Agentless-managed system.

406 IBMSystems Director Systems Management Guide

 v External Storage firmware (including IBM BladeCenter external storage firmware
for IBM BladeCenter S SAS RAID Controller Module and IBM BladeCenter SAS
Connectivity Module.

| Supported System x and BladeCenter systems

| Update manager for System x and BladeCenter supports a subset of available
| System x and BladeCenter systems.

| The following System x and BladeCenter systems are supported by Update

| manager for System x and BladeCenter.
| v IBM System x servers, with the exception of System x iDataplex servers
| v IBM eServer™ xSeries® servers: 206, 226, 236, 246, 260, 306, 346, 366, and 460
| v IBM BladeCenter management modules
| v IBM BladeCenter I/O modules
| v IBM BladeCenter storage modules
| v HS series blade servers with the exception of these machine types:
| – HS20 blade server, machine type 7981
| – HS20 blade server, machine type 8678
| – HS20 blade server, machine type 8832
| – HS40 blade server, machine type 8839
| v LS series blade servers
| v JS21 blade server, machine type 7988
| v JS21 blade server, machine type 8844
| v QS22 blade server, machine type 0793

Starting to monitor and update systems

To monitor and update systems, you must set up the environment correctly,
including choosing systems that you want to be monitored. You must also ensure
that a Check for updates is run periodically, and that someone is periodically
checking systems that have compliance issues raised. Lastly, you must take action
by installing needed updates.

For systems that are to be monitored for update management and compliance
status, it is required that you:
v Make sure that the systems are discovered and not locked.
v Collect inventory on these systems.
1. From the Welcome page, click Manage → Update Manager. The Update
manager summary page is displayed.
2. Click the Getting Started link in the upper right corner of the Update manager
summary page and complete the Getting Started wizard. Using this wizard,
you will choose those systems that you want monitored for update compliance,
and create an update group for updates appropriate to these systems.
3. Click the Settings link in the upper right corner of the Update manager
summary page and complete the Settings task. This task is used to specify
details about the update process. This task also specifies settings that are
unique to AIX and IBM BladeCenter systems.
4. Optional: Create additional update groups, to facilitate update management.
5. Schedule a Check for updates to run right away.

Chapter 7. Updating systems 407

 6. Schedule a Check for updates to run periodically, at least once a week.
7. Review the System Compliance section of the Update manager summary page.
Compliance status will not change on the monitored systems until the Check
for updates is complete and compliance has completed. This can take up to ten
minutes after check for updates completes.
8. If some systems are in need of updates, review the exact compliance issues and
make plans to address them by installing 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.

Updates to IBM Systems Director and IBM Director

The use of a configuration with mixed IBM Director 5.20 and IBM Systems
Director 6.1 systems is discussed here, as well as applying updates to IBM Systems
Director itself.

Update manager cannot be used to migrate to IBM Systems Director 6.1 from any
release of IBM Director.

Considerations for updating systems that have earlier

versions of IBM Director
Consider these points when applying updates to systems that are at a level earlier
than the current level of IBM Systems Director.

Migration to IBM Director 5.20 from IBM Director 5.10 cannot be performed by
update manager.

Migration to IBM Systems Director 6.1 from any version of IBM Director 5.10 or
5.20 cannot be performed by update manager. However, you can upgrade an IBM
Director Agent version 5.20 to a IBM Systems Director 6.1 Common-Agent
managed system using agent manager.

IBM Systems Director supports the updating of systems that are at earlier versions
of IBM Director, provided the updates do not change the version or release level.
This earlier version of IBM Director can be updated:
v IBM Director 5.20, all modification levels
Related tasks
Installing agents

Updating IBM Systems Director

Update manager can be used to obtain and install updates for IBM Systems
Director.

Consider these points when updating IBM Systems Director:

v Ensure that software inventory has been recently collected for the management
server before using update manager.
v IBM Systems Director updates require that IBM Systems Director be restarted
before the updates will be active. This restart is required before additional
updates can be installed. If you are also installing firmware or operating system
updates, these updates might require that the IBM Systems Director Server be
restarted as well. If the update requires a restart but you choose to not permit
these automatic restarts, you must manually restart IBM Systems Director.

408 IBMSystems Director Systems Management Guide

 v It is recommended that you install all updates for a release and not a subset.

To update IBM Systems Director, complete the following steps:

1. Ensure that you have collected the latest inventory for the IBM Systems
Director Server.
2. Click the View updates link on the Welcome page in the upper-right corner.
3. Click Check for updates to run or schedule a check for new updates. When the
check for updates completes, the updates needed by the IBM Systems Director
Server will be displayed in the table.
4. Optional: If your management server does not have a connection to the
Internet, you can download IBM Systems Director updates from this IBM Web
site: www.ibm.com/eserver/support/fixes/fixcentral.
a. On the Fix Central page, from the Product Group drop-down list, select
IBM Systems Director. Click Continue.
b. From the Product drop-down list, select IBM Systems Director, and from the
Installed Version drop-down list, select All. Click Continue. The Identify
Fixes page is displayed. It will process a list of fixes to download. Once the
list of fixes are gathered, the Select fixes and download method page is
displayed.
c. It is highly recommended that you click the Select all option on the Select
fixes and download method page. Also, make sure that the Download
using IBM Director option at the bottom of the page is selected. Click
Continue. The Select fixes page is displayed and will quickly transition to
the Agree to terms and conditions page.
d. Select I agree if you agree to the terms and conditions. The Download files
using Download Director page is displayed.
e. Select Download Now to start the download of the updates.
f. Copy the updates to the management server.
g. Use the update manager Import updates task to import the updates.
5. From the View updates panel, select the updates to install and select the Install
button to start the install wizard.
6. (AIX only) If you are installing IBM Systems Director Version 6.1.1 agent
updates on AIX, you must manually restart Common Agent after applying the
patches.
Related concepts
Considerations for updating systems that have earlier versions of IBM Director

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.

Chapter 7. Updating systems 409

 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 received
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 (TL)
The twice yearly AIX releases, which contain new hardware and software
features and service updates. The first of the twice yearly TLs is restricted
to hardware features and enablement, as well as software service. The
second of the twice yearly TLs includes hardware features and enablement,
software service, and new software features.
Make sure that you install all parts of a TL. Back up your system before
installing a TL.
Service Pack (SP)
A collection of service-only updates (also known as PTFs) that are released
between Technology Levels to be grouped together 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 an SP that is recommended for a given AIX TL. Not all TLls
have a recommended SP level.
Latest level
The most recent level of SP or TL.

Tips for updating AIX

Be aware of these tips and restrictions when you are working with AIX updates:
v Back up your system before installing a TL.
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 In order to perform an installation or installation staging for AIX updates, your
system must meet these requirements:
– An AIX NIM master is required to stage and install the updates.
– A NIM environment is required.
– The AIX NIM master and the AIX managed systems (NIM clients) require a
Common Agent.
– The AIX NIM master cannot be the same system as the management server.

410 IBMSystems Director Systems Management Guide

 v The updates will always be staged to a NIM master, and they will be put into a
directory named /export. When creating the NIM environment, create a separate
file system and mount it onto /export in order to avoid using the root file
system to store updates.
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 TL or an SP 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?.

Update considerations for IBM System x and IBM BladeCenter

Updates to IBM System x and IBM BladeCenter can be installed using the update
manager, but you cannot uninstall or roll back System x and IBM BladeCenter
updates.

Consider these points when updating IBM System x and IBM BladeCenter systems
that are running IBM Director:
v Applying System x and IBM BladeCenter device driver and firmware updates to
IBM Director 5.20 systems is supported.
v Applying IBM System x and IBM BladeCenter device driver and firmware
updates to IBM Director 5.10 systems is not supported.

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 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.
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 passthrough 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.

Update considerations for IBM System x systems

When updating IBM System x systems, review these considerations for device
driver and firmware updates involving IBM Director systems.
v Applying IBM System x and IBM BladeCenter device driver and firmware
updates to IBM Director 5.20 systems is supported. This includes IBM Director
5.20 Common-Agent managed system, Platform-Agent managed system, and
Agentless-managed system.
v Applying IBM System x and IBM BladeCenter device driver and firmware
updates to IBM Director 5.10 systems is not supported.

The IBM System x and IBM BladeCenter platform configuration

file
An IBM System x and IBM BladeCenter platform configuration file can be used to
specify systems that you have not discovered or collected inventory for with IBM
Systems Director. This file is then used to perform update tasks on the systems
listed in the file.

Chapter 7. Updating systems 411

 This capability applies to IBM System x and IBM BladeCenter systems. A blank
IBM System x and IBM BladeCenter platform configuration file is created
automatically on the management server the first time that any IBM 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 IBM 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.

An IBM Director 5.20 updatePlatform.txt file will be migrated to the IBM Systems
Director 6.10 IBM System x and IBM BladeCenter platform configuration file
format automatically.

IBM System x and IBM BladeCenter platform configuration file format

In the IBM 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 usually 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, please use an example entry as a basis for a
new entry to avoid errors.

Tasks used with the IBM System x and IBM BladeCenter platform
configuration file

Use the IBM 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 check for updates task. For each of these update manager tasks, consider these
points:
Check for updates (selected from the Update manager summary)
If the IBM System x and IBM BladeCenter platform configuration file
contains machine type and operating system entries, the Check for Update
panel will display these values. You can use them as you would any other
selection on this page.
If an entry in the IBM 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.

412 IBMSystems Director Systems Management Guide

Check for Updates (selected in the context of a system and then choosing
Custom)
The IBM 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 IBM 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 IBM
System x and IBM BladeCenter platform configuration file that you are
interested in.

Using the IBM System x and IBM BladeCenter platform configuration file to
check for 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 IBM System x and IBM BladeCenter platform
configuration file so that you can check for updates and download updates for
systems that you have not discovered or for which you have not collected
inventory using IBM Systems Director.

To modify the IBM System x and IBM BladeCenter platform configuration file for a
particular IBM System x or IBM BladeCenter system, complete the following steps:
1. Open the file in a text editor. The IBM 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.

Sample IBM System x and IBM BladeCenter platform configuration file:

This sample file can be used to download updates for systems 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:

Chapter 7. Updating systems 413

 #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

Update considerations for Hardware Management Console

(HMC) systems
Hardware Management Console (HMC) systems can have these items installed:
updates, upgrades and interim fixes.

Note these restrictions and hints for working with HMC updates:
v Only HMC Version 7 Release V7.3.3 SP2, and later versions and releases, are
supported.
v Only Virtual I/O Server (VIOS) Version 1.5.2.1 and later fix packs are supported.
v HMC 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.
An ISO image is a disk image for an ISO 9660 file system, and contains the
installable files for a particular update or upgrade.
v 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 HMC upgrades are not supported for the installation task. If you attempt an
installation task, after having successfully performed a manual installation

414 IBMSystems Director Systems Management Guide

 staging task, a message is displayed with instructions for installing the upgrades
on each HMC 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 HMC updates, upgrades, or interim fixes is not
supported.
v Extended discovery or inventory discovery must be performed for the target
HMC before using any HMC update manager functions.
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 HMC 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 HMC 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. IBM i
systems must be a Platform Agent-managed system with access granted.
v Only complete Cumulative PTF packages and PTF Groups can be acquired, not
individual PTFs.
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 will be performed for IBM i
systems.

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 Enterprise
Linux Red Hat Enterprise Linux Version 5 and Enterprise Linux SUSE Linux
SLES Version 10.
v In order to apply Linux updates, each system must be registered with 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 SLES distributions, http://www.novell.com or
http://www.novell.com/customercenter
v All Common Agents must be running at root level.

Chapter 7. Updating systems 415

 v You must have network connectivity between the management server, the target
system, and the Internet. The Internet connection is needed to obtain the
updates from the Linux Distribution Partner.
v The commands yum and rug must be installed on each system that is to receive
an update. If they are missing, no interactive messages are displayed, but the
error logs will indicate this error.
v Uninstalling updates and rolling back updates are not supported.
v The Linux system to receive updates must be a Common-Agent managed
system.

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 (HMC) or
Integrated Virtualization Manager (IVM), extended discovery or inventory
collection must be performed for the managing IVM or HMC of the target
system before using any Power Systems Firmware update manager functions.
v For a stand-alone power system, 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
IBM System p5® Power system firmware.
v All IBM System p6 firmware will be available from the fix service provider.
v Some IBM System p5 and IBM System p6 Power systems have Bulk Power
Control (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 an HMC. 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 IBM System p5 or IBM System p6 Power
systems firmware to a new level and that level requires an update to the bulk
power firmware. Uupdate 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
www14.software.ibm.com/webapp/set2/firmware/gjsn. You can find a
description of firmware at www-941.ibm.com/collaboration/wiki/display/
LinuxP/P5+System+Firmware+Upgrade.
v Some levels of Power Systems Firmware being installed on a system managed
by HMC system have a requirement that the HMC managing the system be at a
minimum HMC level. Consult the readme file for the Power Systems Firmware.
If you attempt to update the Power Systems Firmware when the HMC 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 System Firmware:
v Standalone IBM System p5 and later systems running Linux or AIX, with the
Common Agent installed
v IBM Power Systems p5 and later systems managed by HMC and running Linux,
AIX, or IBM i

416 IBMSystems Director Systems Management Guide

 v IBM Power Systems p5 and later systems (IBM Power Systems p6 and so forth)
managed by IVM, with VIOS 1.5.2.1 and later fix packs

Viewing the Update Manager Summary page

The Update manager summary page is used to launch update tasks. Take the time
to become familiar with this page before starting to manage updates.

If not already done so, collect inventory for all systems to be used by update
manager, so that update inventory is available. This inventory is used to determine
whether acquired updates are needed or applicable to your systems.

To view the Update manager summary page, complete the following steps:
1. On the IBM Systems Director Welcome page, click Manage and then select
Update Manager. The Update manager summary page is displayed.
2. View the System Compliance section. This section indicates the number of
systems that are being monitored by compliance policies, and also which
systems are compliant and which are not. For those systems that are not
compliant, there is an indication of the highest severity of the missing updates.
The links will display a list of systems in each category.
3. Examine the pie chart. This chart helps you understand what percentage of
your systems are in compliance, what percentage are in need of updates, and
the severity of the needed updates.
4. View the Manage section, which lists tasks to be performed on updates.
5. View the Search local updates field. This field is used to search the
user-readable portion of update files for specific character strings, such as the
name of an operating system or a PTF number.
6. View the Getting Started and Settings links, located in the upper right corner.
Click each of these links and to run each of these tasks before you run any
other update functions.

Configuring update manager

Before starting to manage updates, run the Getting Started wizard and Settings
function to customize your configuration.

To specify settings, go to the Update manager summary page, click Getting started
in the upper right of the page, and complete the Getting Started wizard. Then click
Settings in the upper right of the page, and complete the pages that follow.

Getting started with updates

Use the Getting Started wizard to select systems to monitor and specify Internet
connection settings.

The Getting Started wizard is used to:

v Select a set of systems to monitor with compliance policies
v Configure Internet connectivity
v Run or schedule a check for updates

To run the Getting Started wizard, complete the following steps:

1. On the Update manager summary page, click Getting Started in the upper
right corner of the page. The Getting Started wizard displays a welcome
panel.

Chapter 7. Updating systems 417

 2. Optional: Clear Show the welcome page next time if you do not want to see
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 unlocked, 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 in order to check for and 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 Hypertext Transfer Protocol (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.
10. Optional: Click Test Connection if you want to test the connection settings
that you have specified.
11. Click Next. The Summary page is displayed.
12. This page lists the types of updates that will be added to the update group in
order 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 a check for updates for the selected systems.
Schedule this check 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.

Changing update settings

Use Settings to provide Internet connection settings and set a size limit on the
storage location for the updates.

To change settings, complete the following steps:

418 IBMSystems Director Systems Management Guide

1. From the Update manager summary page, click the Settings link in the top
right corner. The Connection page is displayed.
2. Examine and modify the connection settings. This is the same information as
what is displayed on the Connection page of the Getting started wizard.
3. Optional: Click Test Connection. The connectivity to IBM is tested, and you
will receive a message indicating whether the test succeeded or failed.
4. Click Location. The storage location for updates cannot be changed, but you
can view it for reference.
5. Specify the amount of disk storage on the management server that will be
allocated for update files when they are downloaded. Type the maximum size
in megabytes. Update files will not occupy more disk space than the maximum
value specified here.
6. If you are monitoring AIX systems, click AIX and fill-in the page.
7. If you are monitoring IBM BladeCenter systems, click BladeCenter and fill-in
the page.
8. Click OK.

Specifying AIX update settings

For AIX, a NIM master must be specified. This system receives updates to be
installed to other AIX systems. A page in the Settings function is used to do this.

If the AIX NIM master is not chosen before an installation staging for an AIX
update is performed, the Settings function is displayed as part of the installation
staging operation.

If the AIX NIM master is not chosen before an install or uninstall task for an AIX
update is invoked, the same situation occurs - the Settings function is displayed as
part of the operation.

To specify AIX setting, complete the following steps:

1. From the Setting task, click AIX. The AIX page is displayed.
2. Click Browse to see a context chooser with a list of systems.
3. Choose the system that is the AIX NIM master.
4. Click OK.

Specifying IBM BladeCenter update settings

A tab on the Settings function labeled BladeCenter is used to choose which file
transfer protocol and servers are to be used when running the installation staging
and installation tasks.

Note: There is a 64 character limit on the length of the relative path and file names
for updates installed from TFTP servers with SNMP. This includes updates to IBM
BladeCenter Management Modules and IBM BladeCenter Pass-through Modules.
The 64 character limit is for the sum of the lengths of:
v The relative path to updates field
v The specific update’s build identifier
v The update’s firmware file names

Therefore, the relative path to updates field must be kept as short as possible if
IBM BladeCenter Management Modules or IBM BladeCenter Pass-through
Modules will be updated.

Chapter 7. Updating systems 419

 No such length limit applies to switch module updates installed from TFTP or FTP
servers.

Some IBM BladeCenter updates support only using FTP, and some support only
using TFTP. View the update’s properties to see the supported protocols. If an
update supports both TFTP and FTP, TFTP is used.

If no TFTP or FTP server is chosen before an installation staging task is performed,

the Settings function is displayed as part of the installation staging operation.

If no TFTP or FTP server is chosen before an install task is performed, the same
situation occurs - the Settings page is displayed as part of the operation.

To specify IBM BladeCenter settings, complete the following steps:

1. From the Setting task, click BladeCenter. The BladeCenter Settings page is
displayed
2. Select one of these choices to answer this question: Which system do you
want to use as the TFTP server?
v Do not use a TFTP server. If the TFTP server included with the
management server has been enabled, choosing this option will disable it.
You will not be able to install updates on Management Modules and certain
I/O Modules that require a TFTP server if no TFTP server is specified.
v Use the management server as a TFTP server. This starts and uses the
TFTP server included with the management server.
v Use system.
Use a TFTP server on an external system. If the TFTP server included with
the management server has been enabled, choosing this option will disable
it. Select a system. Click Browse to see details about a given system.
3. Select a Network interface (IP address). This option is to choose an alternate
network interface for the server specified in the Use system. selection.
4. In the TFTP root directory field, type the full path to the root directory of the
TFTP server (for example, ’/tftpboot’ or ’C:\Program Files\TFTPServer\
tftpboot’). This path is used to automatically distribute files to the TFTP
server.
5. Optional: In the Relative path to updates field, if the update files are located
in a subdirectory of the TFTP server root directory, specify the relative path of
that subdirectory (for example: ’update_manager/updates’). If no path is
provided, the TFTP server root directory is assumed as the path where the
update files are stored.
6. Select one of these choices to answer this question: Which system do you
want to use as the FTP server?.
v Do not use an FTP server. An FTP server will not be used for the
installation staging and install tasks.
You will not be able to install updates on certain I/O Modules that require
an FTP server if no FTP server is specified.
v Use system
Use an FTP server on an external system. Select a system. Click Browse to
see details about a given system.
7. Select a Network interface (IP address). This option is to choose an alternate
network interface for the server specified in the Use system. selection.

420 IBMSystems Director Systems Management Guide

 8. In the FTP user home directory field, type the full path of the FTP user’s
home directory on the FTP server (for example: ’/home/ftpuser’). This path is
used to automatically distribute files to the FTP server.
9. Optional: In the Relative path to updates field, if the update files are located
in a subdirectory of the FTP user’s home directory, specify the relative path of
that subdirectory (for example, ’update_manager/updates’). If no path is
provided, the FTP user’s home directory is assumed as the path where the
update files are stored.
10. Type the FTP server credentials:
a. User name
b. Password

Note: Anonymous FTP (user name of ’anonymous’) is supported. However,

for Anonymous FTP, the need for a password (or the form of the password) is
a requirement of the FTP server itself.
11. Click OK to have these choices take effect.

Managing updates
Managing updates consists of working with update groups, performing actions on
updates, and viewing detailed information about updates. The actions that can be
performed on updates include installation, downloading, and deleting files. The
detailed information about updates include update documentation, applicable
systems and releases, and prerequisite updates.

Managing update groups

You can group updates together 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.

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.

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.

Chapter 7. Updating systems 421

 Note: For more information about navigating and working with tables in IBM
Systems Director Web interface, see “Table navigation in IBM Systems Director.”

To view an update group, complete the following steps:

1. From the Update manager summary page, locate the Manage section.
2. Click Show Update Groups. A table of all defined update groups is displayed.
This table shows all the update groups in the group named All Update Groups.
3. Click the name of the update group that you want to view. The members of the
group are displayed in a list.

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 similar to those on the
Check for Update page.
7. Click Next. The Summary page is displayed.
8. Review the choices for the new group carefully.
v If your choices are correct, Click Finish to create the new update group.
v If you want to make a change, click Back to go to the previous page, or
choose the Group Editor wizard page from the navigation area.

Performing actions on updates

Updates can be acquired, downloaded, staged, and installed in order to keep your
systems current.

It is suggested that you set up compliance policies, and review the results before
performing any other actions on updates. This way, you can determine which
systems need updates, and prioritize their installation based on the importance of
each update.

Update actions can be performed only on systems that are unlocked. If a system is
locked, the update menu actions will not be displayed for it. You cannot select a
locked system in any of the system selection actions (System page in the Install
wizard, Installation staging wizard, and so forth).

Before performing these tasks, verify that your settings are correct. Click the
Settings link from the upper right corner of the Update manager summary page
and view the settings to ensure that they are correct.

422 IBMSystems Director Systems Management Guide

To perform actions on updates, complete the following steps:
1. Select an individual update and click Actions.
2. Click one of the tasks from the list.

Checking for new updates

Use the Check for updates task to periodically check for new updates that update
manager currently does not know about, and obtain the information necessary to
include them. Schedule a Check for updates to run periodically and frequently, at
least once a week.

The Check for updates task is not monitoring or reviewing any of your systems for
updates. That task is performed by the use of compliance policies. If you do not
have compliance policies set up, the check for updates task will not find any
updates. This is not considered an error condition.

To check for new updates, complete the following steps:

1. Select Check for updates from the Manage section of the Update manager
summary page. The Check for updates page is displayed.
2. Select the types of updates that you want to check from the Available update
types list and click Add to move them to the Selected update types list.
3. Optional: Click Remove to remove any entries that have been selected in
error.
4. Click OK. A scheduling task is displayed
5. Optional: Type a job name.
6. 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 check.
You are advised to schedule a repeating check, 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.
7. Click Notifications and enter notification options.
8. Click Options and enter other options.
9. Click OK.
10. 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. Visit the Navigate Resources area

and select a system or system group. Click Actions → Release Management →
Check for Updates. This will scope the check for updates to just that type of
system or systems in the group.

From this path, you can optionally choose to perform a check for updates based on
the compliance policy of the system.

Tip: Schedule a Check for updates to run periodically and frequently, at least once
a week.

Chapter 7. Updating systems 423

 Adding updates to a compliance policy
Updates can be added to a compliance policy, in order 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.

Downloading updates
While the download of updates will happen 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 desired time of installation.

You can choose to download the update’s installable files 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 update’s installable files have
not been downloaded when the install task is scheduled, the download task will
automatically be invoked before the install task.

It is important to note that the membership of an update group is not resolved at

the time that a task using the groups is scheduled. The membership of the update
group is resolved at the time that the task runs.

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 of 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.

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.

424 IBMSystems Director Systems Management Guide

When you select the download task on an update’s context menu, a panel is
displayed to guide you through visiting the appropriate Web site, downloading the
update, and then copying the update’s installable files.

To perform a manual download of an update, complete the following steps:

1. From the update’s 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 update’s installable files.
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 update’s installable files. 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’s 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.

Once an update has been manually downloaded, it can be managed the same way
as any other update.

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 will be staged when it is needed. This task is provided in order 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 update’s installable files from the management server to an
appropriate location for eventual installation.

If the update’s installable files have not been previously downloaded, a download
will be run before the installation staging is performed.

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.

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 Welcome 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.

Chapter 7. Updating systems 425

 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 update requirements. 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 update requirements is selected. You cannot edit the
required updates here.
11. Click Next. The Summary page is displayed.
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.

Installing updates
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.

To install updates, complete the following steps:

1. From the Update manager summary page, locate the Manage section.

426 IBMSystems Director Systems Management Guide

 2. In the Common Tasks section, click Install updates. The Install Wizard
Welcome page is displayed.
3. Clear Show this welcome page next time if you do not want to see the
Welcome page next time.
4. Click Next. The Updates page is displayed.
5. Select each update that you want to install. Whole update collections, not
individual member updates, will be installed.
6. Click Add. The Systems page is displayed.
7. Select each system or system group that you want to install the updates and
click Add. All selected updates that are needed by or applicable to the
selected systems will be installed. If you select a system group, the updates
are installed on those systems that are a member of the group at the time that
the install task runs.
8. 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.
9. Click Next. The Options page is displayed.
10. Clear Automatically install missing update requirements if you do not want
updates required for the installation of the selected updates to also be
installed. Clearing this box is not advised. Missing mandatory updates will
cause the installation to fail.
11. If there are updates that are required for the installation of the selected
updates, these updates are displayed in the Missing Update Requirements
table.
a. Select a system from the list of systems to see the update requirements for
each system.
b. You cannot change anything here, only view it. The data displayed here
can lead you to change your choice for Automatically install missing
update requirements, however.
12. 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 will be 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.
13. Click Next.
14. 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.
Note that 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.

Chapter 7. Updating systems 427

 15. 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.
16. 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 install task will complete with
errors and some update installs might not be attempted if a dependent update
requires an immediate restart.
17. Click Restart values to view all updates to be installed on the system and
their individual restart requirements. This view is specific to the system for
which the restart value was selected. 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, return
to the install wizard, click Back, and remove systems or updates.
Be aware that 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.
These are the possible values:
Immediate
The restart must be performed before other updates can be installed
or uninstalled.
Deferred
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.
18. Click Next. The Summary page is displayed.
19. 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 task.
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.

Uninstalling updates
It may 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, locate the Updates section.
2. Click Show installed updates.
3. Verify that the updates that you are trying to uninstall have been installed on
the target system or system group.
4. Select Uninstall updates. The Uninstall Wizard Welcome page is displayed.
5. Clear the Show this welcome page next time check box if you do not want to
see the welcome page next time.
6. Click Next. The Updates page is displayed.
7. Select each update that you want to uninstall and click Add.

428 IBMSystems Director Systems Management Guide

 8. Click Next. The Systems page is displayed.
9. Select each system or system group from which you want to uninstall the
updates. 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 uninstall task
runs.
10. 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.
11. Click Next.
12. Clear Automatically uninstall dependent updates if you do not want to
uninstall the updates that depend upon the updates that are chosen to be
uninstalled. Clearing this box is not advised. Failing to uninstall dependent
updates will cause the uninstall task to fail.
13. A table of the known update dependencies for each selected update is
displayed.
a. Select a system from the list of systems to see the update dependencies for
each system.
b. You cannot change anything here, only view it. The data displayed here
can lead you to change your choice for Automatically uninstall
dependent updates, however.
14. Optional: The Manual Uninstall Required page might be displayed. It is
displayed only when an update selected for uninstall 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.
15. 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.
16. 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 uninstall task will complete
with errors and some uninstalls might not be attempted if a dependent update
requires an immediate restart.
17. Click Restart values to view all updates to be uninstalled on the system and
their individual restart requirements. This view is specific to the system for
which the restart value was selected. 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,
return to the uninstall wizard, click Back, and remove systems or updates. Be
aware that if you have selected system groups as the target for the uninstall
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.
These are the possible values:
Immediate
The restart must be performed before other updates can be installed
or uninstalled.

Chapter 7. Updating systems 429

 Deferred
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.
18. Click Next. The Summary page is displayed.
19. Review the information on this page.
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.
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.

If an update cannot be uninstalled, it may be possible to rollback 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.

Importing updates
Use the Import update 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 manager summary page, locate the Updates section.
2. Click Import updates.
3. In the Path field, type the directory of the update files on the management
server. All updates found within the specified directory will be copied to the
update library. You cannot select specific updates from this directory.
4. Click OK. The scheduler is displayed. You can then choose to run the task now
or to schedule it to run in the future.

Any updates that can be generated in the specified directory, will attempt to be
generated and imported also. More information on update generation can be found
by viewing the importupd command and the -g option.

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 those that you want to export.
2. Click Actions → Export updates.
3. Specify a location for the update files by typing 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.

Removing update files

When an update is no longer needed, you can remove its associated installable
files in order 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 the Solution Deployment Descriptor and any

430 IBMSystems Director Systems Management Guide

 human-readable files such as readme files, are 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.

Viewing information about updates

Information about updates and updates groups is often needed to decide whether
to install the update.

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. These are the resources types
that are included in the Updates perspective:
v systems
v updates
v update collections

Click on 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.

Chapter 7. Updating systems 431

 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 imported or 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.

Displaying recently found updates

Updates that have recently become available are of importance to you, as they can
be critical fixes or useful enhancements. Use the Show updates function to
periodically display these new updates, read their details, and decide whether to
download and install them on your systems.

The All updates group, which is predefined, can be used to perform similar work.

Note: For more information about navigating and working with tables in IBM
Systems Director Web interface, see “Table navigation in IBM Systems Director.”

To view a list of recently found updates, complete the following steps:

1. From the Update manager summary page, locate the Manage section.
2. Click Show updates. The Show updates page is displayed.
3. Select a time period for searching for recently found updates. The contents of
the page will automatically change to show a list of updates matching the
selected time period.
4. Optional: Click Search this table to search within the table for particular
updates of interest.
5. Select an update.
6. You can perform all the update functions available from any table of updates.
You can display the update actions and choose any of these: download,
installation staging, installation, and so forth. You can also use any of the table
level actions such as sort, search, filter, and so forth.
7. Click Close when finished.

432 IBMSystems Director Systems Management Guide

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 on the update’s name. A
page of general information about the update is displayed, including: name, ID,
size, version, and so forth.
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.
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.
File names
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:
Immediate
The restart must be performed before other updates can be
installed or uninstalled.
Deferred
The restart can be performed at the end of the install or
uninstall task.

Chapter 7. Updating systems 433

 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
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.

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 it’s 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 desired search terms.

434 IBMSystems Director Systems Management Guide

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 take actions 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:
IBM Matches anything that contains IBM.
IBM* Matches anything that begins with IBM.
IBM server
Matches anything that contains either IBM or server or both.
IBM OR server
Same as IBM server.
+IBM +server
Matches anything that contains both IBM and server.
IBM AND server
Same as +IBM +server.
+IBM -Blade
Matches anything that contains IBM and does not contain Blade.
clock~ Matches anything similar to clock, such as block, click, clocks, and so forth.
(IBM OR server) AND Blade
Matches anything that contains Blade and also contains IBM or server or
both.
″Issues and Recommendations″
Matches anything with the exact phrase ’Issues and Recommendations’.

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’s context 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.

Note: For more information about navigating and working with tables in IBM
Systems Director Web interface, see “Table navigation in IBM Systems Director.”

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.

Chapter 7. Updating systems 435

 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.

Note: For more information about navigating and working with tables in IBM
Systems Director Web interface, see “Table navigation in IBM Systems Director.”

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.

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’s 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.

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.

436 IBMSystems Director Systems Management Guide

 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.

Keeping systems in compliance

Use compliance policies so that you are informed of systems that are missing
specific updates.

The Update manager summary page gives you a quick view of the number of
systems that are being monitored by compliance policies, and the number of
systems that are out of compliance. Review this information before viewing the
more detailed data described below.

All compliance policy tasks are initiated from the System Tasks group of the
System compliance section on the Update manager summary page. Use the
Update manager summary page to view information about your systems, their
update requirements, and their compliance policies:
1. To see installed updates for a system or system group, click Show installed
updates from the Update manager summary page. You then select a system or
system group.
2. To see needed updates for a system or system group, click Show needed
updates from the Update manager summary page. You then select a system or
system group.
3. To view or edit update compliance policies, click Change compliance policies
from the Update manager summary page. This brings up a list of systems. You
can then select a system and edit the compliance policy for that system.

You can select systems or system groups. If a policy is inherited for a system
because the system is in a group that is in a compliance policy, there is a table field
that indicates ’Inherited’.

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 System Compliance
section. This section provides a quick summary of the update health of your
systems and provides several system-related tasks.

If you see the term Inherited Compliance Policy, or a field named Inherited in a table
when you are viewing this information, there is a compliance policy on a system’s
parent group. The policy can be removed from the system only by removing it
from the systems parent group.

Tips

The behavior of a compliance policy for an update group differs slightly

depending on whether the update group is static or dynamic. This is the default
behavior and can be changed by modifying the compliance policy.
v 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.

Chapter 7. Updating systems 437

 v 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 will not be considered when the parent
system or update group is used for validation of compliance policies.

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.

You cannot explicitly add a new compliance policy without adding a system or
system group to be monitored. Every time that a system is selected for update
monitoring, it is given a compliance policy. The only way to delete the compliance
policy is to remove the system from update monitoring.

Modifying compliance policies

Use the Change Compliance Policies page to change compliance policies.

The Change 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, and has an associated type.

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, locate the System Compliance
section.
2. From the System Tasks group, click Change compliance policies. The
Compliance Policy page is displayed.
3. Select a system or system group.
4. 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.
5. Click Show Compliance Policy. A table of updates and update groups
currently included in the compliance policy is displayed
6. Choose a task:
v Click Add to insert a new compliance check.
– Choose the updates or update groups to be included in the compliance
policy.
– If an update group is selected,
Click Ensure that all applicable updates are installed to indicate that the
compliance policy will be successful only if all applicable updates in the
group are found to be installed on the system.
Click Ensure that at least one applicable update is installed to indicate
that the compliance policy will be successful if one or more updates in the
group is found to be installed on the system.
v Select and edit compliance checks that are for update groups. You cannot
edit compliance checks that are for individual updates.
v Select and remove compliance checks from the table.

438 IBMSystems Director Systems Management Guide

 7. Click OK to add the updates or update groups to the compliance policy.
8. Click Save to make permanent the changes to the compliance policy.

If you remove all updates or update groups from the policy and clicks Save, you
are in effect removing the policy for the selected system or system group.

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.

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 being 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 four
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

Chapter 7. Updating systems 439

 To identify systems that are out of compliance, complete the following steps:
1. On the Update Manager summary page, find the System Compliance section.
2. Examine the pie chart and icons to its right. The number of systems in each
compliance category is displayed.
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 brings up a table of
systems.
4. Optional: You can also click on 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 together, 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.

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
taking into consideration 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 systems being monitored, or as
indicated by the pie chart on the Update manager summary page.

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 displayed status 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 will start.
You can choose to resolve all issues at once instead of resolving them
individually.

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.

440 IBMSystems Director Systems Management Guide

 Update tasks such as Uninstall can be done from this page by clicking Actions and
selecting an available task.

To change which update properties are displayed on the table, their position in the
table, or the field sizes, click Actions → Columns.

Note: For more information about navigating and working with tables in IBM
Systems Director Web interface, see “Table navigation in IBM Systems Director.”

To see a list of updates installed on a particular system, complete the following

steps:
1. From the Update manager summary page, locate the System Compliance
section.
2. Click Show installed updates from the System Tasks group. The Show
Installed 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 installed updates. A table of installed updates is displayed.
5. Examine the table. There is one line for each update and details about the
update.

Showing needed updates

Use the Show needed updates function to identify updates that are needed by
your systems.

This function does not show information for systems that you have not done an
inventory discovery on.

Note: For more information about navigating and working with tables in IBM
Systems Director Web interface, see “Table navigation in IBM Systems Director.”

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 update inventory on your systems. This
task does not list as needed any update that IBM Systems Director does not know
about, even if one or more systems needs it or if the update has been reported by
inventory on another system. That is why it is important to schedule and review
the results of the Check for updates task.

To see a list of updates needed by a system, complete the following steps:

1. From the Update manager summary page, locate the System Compliance
section.
2. Click Show needed updates from the System Tasks group. The Show Needed
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 needed updates. A table of needed updates is displayed.
5. Examine the table. There is one line for each update and details about the
update.

Chapter 7. Updating systems 441

 Update tasks such as Install can be done from this page by clicking Actions and
selecting an available task.

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 (TL) or Service Pack (SP). This choice
copies all the TL and SP metadata to the management server.
Update to recommended level
Update to the recommended SP level. When an AIX system is chosen from
the Getting Started wizard, this type is the default value. If the newest TL
does not have a recommended SP, the AIX system will be updated to the
newest TL that does have a recommended SP.
Update to latest level
Remain on the same TL, but update to the latest SP level.
Upgrade to latest level
Upgrade the TL to the latest level. Usually, AIX is updated to a new SP on
the new TL.

Update types for System x and IBM BladeCenter

These are the update types for System x and IBM BladeCenter systems.
System x and Blades
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 (not sure this is used on
current systems)
iSCSI Internet SCSI updates

442 IBMSystems Director Systems Management Guide

 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
SP Driver
Service Processor (including RSA and RSA II) Device
Driver updates
Tape Tape Drive firmware updates
UXSP UpdateXpress System Pack
Video Video Device Driver updates
Severity
Initial Release
Critical
Suggested
Non-Critical
BladeCenter
Categories
Switches
Out of band I/O Module updates
Management Module
Management Module and Advanced Management Module
firmware updates
Severity
Initial Release
Critical
Suggested
Non-Critical

When chosen from the Getting Started wizard, all IBM System x updates are
selected by default.

Update types for HMC

These are the update types for Hardware Management Console (HMC) systems.
All Used to request all updates.

Chapter 7. Updating systems 443

 Update to recommended level
Remain on the same version and release, but update to the recommended
modification level. This is the default when an HMC system is chosen from
the Getting Started wizard.
Update to latest level
Remain on the same version and release, but update to the latest
modification level.
Upgrade to recommended level
Upgrade the version and release to the recommended level.
Upgrade to latest 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.
IBM Director
5.20 IBM Director 5.20
6.1 IBM Systems Director 6.1

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 DB2 UDB, High Impact or Pervasive and other PTF
Groups. The list of PTF Groups will vary depending on the IBM i
version being updated.
WebSphere PTF Groups
Includes updates for WebSphere® products supported by IBM i.
The list of PTF Groups will vary 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.

444 IBMSystems Director Systems Management Guide

 Enhancements
New features
Novell SUSE Linux Enterprise Server
Category
v Recommended
v Optional
v Security

Update types for Power Systems Firmware

These are the update types for Power Systems Firmware.
All Used to request all updates.
Update to recommended level
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.
Update to latest level
Remain on the same version and release, but update to the latest
modification level.
Upgrade to recommended level
Upgrade the version and release to the recommended level.
Upgrade to latest level
Upgrade the version and release to the latest level.

Chapter 7. Updating systems 445

446 IBMSystems Director Systems Management Guide
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 systems must have been discovered and
unlocked, and 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.
Hardware Command Line Interface
Invokes the hardware command line facility.
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.

© Copyright IBM Corp. 1999, 2009 447

 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” on page 451

File transfer
File transfer is used to send files from one location to another and to synchronize
files, directories, or drives. The file transfer task is a secure alternative to File
Transfer Protocol (FTP).

You can transfer individual files and directories between the following systems:
v The browser system and the management server
v The browser system and a managed system
v The management server and a managed system

Transferring files directly between two systems, neither of which is the

management server nor the browser system, is not supported. However, you can
transfer a file from one system to the management server or browser system, and
then transfer that file to another system.

Icon File transfer icon

Supported IBM Systems with Common Agents
Systems Director
objects
Supported operating All operating systems supported by IBM Systems Director
systems
Availability Part of the standard IBM Systems Director installation
Required hardware or None
hardware limitations
Required software None
Required protocols None
Required device None
drivers
Mass Configuration No
support
Scheduler support No
Files associated with None
this task
Events associated with None
this task

Hardware command line

The hardware command line function, also know as IBM Management Process
Command-Line Interface (MPCLI), is run from an established remote session.

MPCLI provides system management functions from an easy-to-use command-line

interface that connects to a service processor. Using MPCLI, you can access and set

448 IBMSystems Director Systems Management Guide

 a wide range of information about the health, configuration, communication, and
state of your system. These functions are immediately available after you make a
connection to a service processor.

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 manages a command-line interface to the remote
system, on a management console.

You can have multiple remote command-line sessions active at the same time. You
can have only one active remote command line session through a management
server to a single system at a time.

You can use the remote command line window to establish a fully active command
session with a system. A remote command line session is non-graphical, so a
command line window opens when it is started.

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 only the Telnet protocol.

By default, remote command line uses Transmission Control Protocol (TCP). If you
disable support for TCP sessions, remote command line uses User Datagram
Protocol (UDP).

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 these applications installed, you must first
obtain it.
BladeCenter and RSA Remote Control
Launch the Web interface for remote control of IBM BladeCenter or Remote
Supervisor Adapter (RSA) systems.
Microsoft Windows Remote Desktop Connection
Launch this application for Windows systems
Virtual Network Computing
Launch Virtual Network Computing (VNC) for AIX and Linux systems.

If your system does not have one of these applications installed, you must first
obtain it. To install and configure a remote control application, go to the Remote
Access Summary page and click Set up remote control in the Common Tasks
pane.

Chapter 8. Remotely accessing systems and resources 449

 IBM BladeCenter and RSA Remote Control
Use the IBM BladeCenter and Remote Supervisor Adapter (RSA) function to access
an IBM BladeCenter or RSA system.

Microsoft Windows Remote Desktop Connection

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.

Virtual Network Computing

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.

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
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

450 IBMSystems Director Systems Management Guide

 Related tasks
“Using the serial console” on page 459

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.

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
running on AIX. Otherwise, you will get an error message.

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 ....

Chapter 8. Remotely accessing systems and resources 451

 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” on page 447

Using the Distributed Shell to issue a command to several

targets
You can use the Distributed Shell to issue a command to several targets.

To use the Distributed Shell, you must be logged into IBM Systems Director Server
running on AIX. Otherwise, you will get an error message.

Before doing this task, a set of Operating System targets must be discovered and
you must request access to those targets.
1. In the IBM Systems Director Web interface navigation area, click Navigate
Resources.
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.

452 IBMSystems Director Systems Management Guide

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
running on AIX. Otherwise, you will get an error message.

Before doing this task, a set of Operating System targets must be discovered and
you must have access to those targets.
1. In the IBM Systems Director Web interface navigation area, click Navigate
Resources.
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.

To use the Distributed Shell, you must be logged into IBM Systems Director Server
running on AIX. Otherwise, you will get an error message.

Before doing this task, a set of Operating System targets must be discovered and
you must have access to those targets.
1. In the IBM Systems Director Web interface navigation area, click Navigate
Resources.
2. Navigate to a target.
3. Right-click the target and select System Configuration → Remote Access →
Distributed Command. The Distributed Shell page is displayed.
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.

To use the Distributed Shell, you must be logged into IBM Systems Director Server
running on AIX. Otherwise, you will get an error message.

Before doing this task, a set of Operating System targets must be discovered and
you must have access to those targets.
1. In the IBM Systems Director Web interface navigation area, click Navigate
Resources.
2. Navigate to a target.
3. Right-click the target and select System Configuration → Remote Access →
Distributed Command. The Distributed Shell page is displayed.
4. Click Browsed Saved Commands .... The Saved Commands window is
displayed.

Chapter 8. Remotely accessing systems and resources 453

 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.

Transferring files and directories

Use the file transfer task to transfer files and directories from one system to
another.

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.

Important:
v You can use the file transfer 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 transfer.

To transfer files, complete the following steps:

1. From the Remote Access Summary page, click File Transfer. The Targets page
is displayed.
2. Select the targets for file transfer, 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 Transfer page is displayed.
4. In the Source File System pane, expand the applicable disk file system. The
contents of that file system are displayed, showing subdirectories and files.

Note: You can switch between Local (management console) and Director
Server (management server) by clicking the arrow in the Source File System
pane and selecting your choice.
5. Locate and highlight the source file or directory in the Source pane (that is, the
local system or management server).

Note:
v You can select multiple files for transfer by pressing and holding the Shift
key while clicking the desired files with the mouse. When you select the last
file in the group to be transferred, release the Shift key but not the mouse
button; while still holding the mouse button down, drag the cursor to the
target File System pane.
v Using the wildcard function, you can filter which files are displayed in the
Source File System or Target File System panes. When the File Transfer
window opens, the Name field contains *.* by default.
6. Locate and highlight the destination drive and directory in the Target pane
(that is, the management server or selected system).
7. Select Actions → Source → Transfer Files to Target.

454 IBMSystems Director Systems Management Guide

Synchronizing files, directories, or drives
When you synchronize files, directories, or drives, you replace the contents of the
target file, directory, or drive with the contents of the source file, directory, or
drive, so that the data is identical on both systems.

You can synchronize a source file, directory, or drive with as many target-system
files, directories, or drives as you choose, but you must synchronize the file,
directory, or drive on each system individually. You cannot synchronize multiple
target systems from a source system at the same time.

Attention: Files or directories that are present in the selected files, directories, or
drives on the target system, but not in the selected files, directories, or drives on
the source system, are deleted after synchronizing.

To synchronize files, directories, or drives, complete the following steps:

1. On the Remote Access Summary page, click File Transfer.
2. Select a file on both the source and target systems.
3. Choose the direction of the synchronization:
v If you want the source to be identical to the target, go to the Source File
System pane and right-click the source. Then, click Synchronize from Target.
v If you want the target to be identical to the source, go to the Target File
System pane and right-click the target. Then, click Synchronize from Source.
4. If you receive a message indicating that the selected names are different, click
Yes to continue. The selected files, directories, or drives are now synchronized.

Changing the encoding for a file

A file encoding is a mechanism or standard for representing characters as bytes or
sets of bytes, within a file. The file transfer task of IBM Systems Director is used to
change the encoding for a chosen file.

To change the encoding for a file, complete the following steps:

1. Click on a file from the File Transfer window. The File Editor window is
displayed.
2. Click Options → Change encoding. The Change Encoding panel is displayed.
3. Select an encoding.
4. Click OK.

Using the hardware command line

Use the hardware command line, also known as IBM Management Process
Command Line Interface (MPCLI), for a command-line session with remote
systems that have hardware that is compatible withe MPCLI.

When using the hardware command line 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.

Hardware command line communicates with Remote Supervisor Adapter (RSA),

RSA II, Baseboard Management Controller (BMC), IBM BladeCenter Management
Module, or IBM BladeCenter Advanced Management Module. To use the hardware
command line, complete the following steps:
1. From the Remote Access Summary page, click Launch Command Line
Interface. The Targets page is displayed.

Chapter 8. Remotely accessing systems and resources 455

 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 hardware command line.
4. Click OK. A window with a hardware command line is displayed and enabled
for input.
5. Communicate with the system by issuing commands.
6. Optional: You can select text within the hardware command line window and
click Edit → Copy to copy the selected text to the clipboard. You can also import
clipboard text into a hardware command line window by clicking Edit → Paste.
7. When you are finished, click File → Close to terminate the session.

Establishing a remote command-line session

Use remote command line to run commands on a remote system.

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 command-line session, complete the following steps:

1. From the Remote Access Summary page, click Remote command line. The
Targets page is displayed.
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.
3. Optional: Click Show to filter the targets, for example, to show only those
targets that support remote command line.
4. Click OK. A window with a remote command line is displayed and enabled for
input.
5. Communicate with the remote system by issuing its operating system’s
commands.
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.

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:

456 IBMSystems Director Systems Management Guide

 1. From the Remote Access Summary page, click Launch Web Browser. The
Targets page is displayed.
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.
3. Optional: Click Show to filter the targets, for example, to show only those
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.

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 http://www.microsoft.com/windowsxp/using/
mobility/getstarted/remoteintro.mspx 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.

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.

Establishing Virtual Network Computing communications

Use Virtual Network Computing (VNC) to communicate with systems with a
full-screen session.

Chapter 8. Remotely accessing systems and resources 457

 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.

To establish a VNC 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 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.

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:
1. From the Remote Access Summary page, click Remote Control. The Targets
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.

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
Targets page is displayed.
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.
3. Optional: Click Show to filter the targets, for example, to show only those
targets that support remote Xen console.
4. Click OK. A window with a remote Xen console is displayed and enabled for
input.

458 IBMSystems Director Systems Management Guide

 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.

Using the serial console

Use the serial console to open console windows to one or more POWER managed
systems.

Note: This task requires the IBM Systems Director Launched Tasks program. This
program is installed automatically the first time you use a task that requires it. For
information about the IBM Systems Director Launched Tasks program, see
“Starting the IBM Systems Director Launched Tasks program.”

To use the serial console, you must be logged into IBM Systems Director Server
running on AIX 6.1F or higher. Otherwise, you will get an error message.

When you use the serial console to open console windows to one or more POWER
managed systems, each window provides access to the system’s serial console,
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, to show only those
targets that support hardware command line.
4. Click OK. A separate window is displayed for each selected target. The title of
each console window will be the display name of the selected target.

Note: The defaults cannot be changed when displaying the serial console using
the IBM Systems Director Web interface.
Related concepts
“Serial Console” on page 450

Displaying a serial console to one server target

You can display a serial console to one server target from the IBM Systems
Director Navigate Resources page.

Note: This task requires the IBM Systems Director Launched Tasks program. This
program is installed automatically the first time you use a task that requires it. For
information about the IBM Systems Director Launched Tasks program, see
“Starting the IBM Systems Director Launched Tasks program.”

To use the serial console, you must be logged into IBM Systems Director Server
running on AIX 6.1F or higher. Otherwise, you will get an error message.

Before doing this task, you must have access to the target’s managing hardware
control point.
1. In the IBM Systems Director Web interface navigation area, click Navigate
Resources.

Chapter 8. Remotely accessing systems and resources 459

 2. Navigate to the target for which you want to display a serial console.
3. Right-click the target and select System Configuration → Remote Access →
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 Navigate Resources page.

Note: This task requires the IBM Systems Director Launched Tasks program. This
program is installed automatically the first time you use a task that requires it. For
information about the IBM Systems Director Launched Tasks program, see
“Starting the IBM Systems Director Launched Tasks program.”

To use the serial console, you must be logged into IBM Systems Director Server
running on AIX 6.1F or higher. Otherwise, you will get an error message.

Before doing this task, you must have access to the target’s managing hardware
control point.
1. In the IBM Systems Director Web interface navigation area, click Navigate
Resources.
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 Navigate
Resources. 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.

Note: This task requires the IBM Systems Director Launched Tasks program. This
program is installed automatically the first time you use a task that requires it. For
information about the IBM Systems Director Launched Tasks program, see
“Starting the IBM Systems Director Launched Tasks program.”

To use the serial console, you must be logged into IBM Systems Director Server
running on AIX 6.1F or higher. Otherwise, you will get an error message.

Close the serial console by using one of three methods:

v File → Close
v X from the console title bar
v Ctrl-x

460 IBMSystems Director Systems Management Guide

Chapter 9. Managing agents
You can use IBM Systems Director to install agents on managed systems, and you
can configure IBM Systems Director to use a different agent manager than its own
embedded agent manager.

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 and are distributed by other management products such as Tivoli
Provisioning Manager. When referring to these common agents generically,
lowercase text is used.

Common agent services

IBM Systems Director uses the common agent services (CAS) architecture, which
provides a shared infrastructure for managing systems. This infrastructure 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 25.

IBM Systems
Director Server

Resource manager

Embedded agent Common agents

manager

Figure 25. The elements of common agent services in the default configuration for IBM Systems Director

Resource manager

Installed on the management server, the resource manager is the management

application, such as IBM Systems Director Server, that uses the agent manager for
security and credential management.

© Copyright IBM Corp. 1999, 2009 461

 Note: Except for security and credential management, systems management
communications between IBM Systems Director Server and common agents do not
go through the resource manager.

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.
v Each Common Agent can use exactly one agent manager.
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 25 on page 461, IBM Systems Director Server includes an

embedded agent manager. However, IBM Systems Director Server can use an
external agent manager instead of the embedded one. Using an external agent
manager allows multiple instances of IBM Systems Director Server to manage the
same common agents. Installing IBM Systems Director Server and agent manager
on separate servers can also improve performance.

Note: The agent manager that is embedded with IBM Systems Director Server can
be used by any instance of IBM Systems Director Server, but it is not configured
for use with other management applications.

The agent manager has the following parts:

agent manager service
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.
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

462 IBMSystems Director Systems Management Guide

 agent recovery service
The agent recovery service is a network service that provides error logging
for common agents that cannot communicate with other agent manager
services. This can occur because of configuration or network problems,
because of missing, expired, or revoked security certificates, or because the
common agent is not yet registered.
To allow common agents to contact it, the agent recovery service
embedded with IBM Systems Director Server listens on the unsecured
(non-SSL encrypted) port 9513.

Note: If you are using an agent manager that was installed separately
from IBM Systems Director, the agent recovery service might be configured
to listen on up to two unsecured ports.

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.

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 and are distributed by other management products such as Tivoli
Provisioning Manager. When referring to these common agents generically,
lowercase text is used.
v Each Common Agent can use exactly one agent manager.
v Each Common Agent can be managed by one or more instances of IBM Systems
Director Server1.
Related information
Tivoli Provisioning Manager documentation

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.

Note: If you install IBM Systems Director Server from the DVD media, it is
installed with the agent packages. If you install IBM Systems Director Server from
the Web download file, however, you need to download the agent tcdriver
packages separately from the “IBM Systems Director 6.1 Agents for Remote
Deployment with Agent Installation wizard” section of the Web download site.
Copy the packages to a location of your choice on the IBM Systems Director Server
system and then import them with the Agent Installation Wizard.

1. All instances of IBM Systems Director Server must be using the same agent manager, and the Common Agent must be registered
with that agent manager.

Chapter 9. Managing agents 463

 These 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.

Note: You can also download the manual agent installation packages from the
“IBM Systems Director 6.1 Agents for Manual Deployment” section of the Web
download site, then copy the self-extracting script and the response file from the
package to a local directory and deploy using the Agent Installation Wizard. The
local directory into which you copy the script and response file depends on which
operating system and version of IBM Systems Director you are running:
v On AIX or Linux:
| – <install_root>/packaging/agent/common/<platform>/6.1.1
– <install_root>/packaging/agent/common/<platform>/6.1
– <install_root>/packaging/agent/platform/<platform>/5.20.3
v On Windows:
| – <install_root>\packaging\agent\common\<platform>\6.1.1
– <install_root>\packaging\agent\common\<platform>\6.1
– <install_root>\packaging\agent\platform\<platform>\5.20.3
1. Start the Agent Installation Wizard. You can start the wizard in multiple ways:
v From the Welcome page, click Start. Then, click Install agents on systems.
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 package that you want to install in the Available list.
b. Click Add. The selected agent package is displayed in the Selected list.

Notes:
v Depending on how you started the Agent Installation Wizard, one or
more agent packages might already be displayed in the Selected list.
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, one or
more systems might already be displayed in the Selected list.
v Depending on the agent package being installed, some selected systems
might not be 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 for installing the selected agent package before
allowing you to continue:

464 IBMSystems Director Systems Management Guide

 – 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.
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.
7. 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 e-mail notification is
sent. You can specify that the e-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 e-mail address, e-mail server, and e-mail server port.

Tip: You can provide only one e-mail address.

8. 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.
9. Click OK to save the job.
Click Cancel to exit from the Run window without saving the job.

Chapter 9. Managing agents 465

 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 Run window so that you can correct the job.
The job created by the Agent Installation Wizard will transfer the agent
self-extracting script and the agent response file into the /tmp directory on the
target system. After the files are copied, the installation file sets are extracted
into the /tmp/extract_XXXXXX 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”.

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
Redwiki at http://www-01.ibm.com/redbooks/community/display/
director/IBM+Systems+Director+6.1+for+Power+Systems. 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.
Related tasks
Install IBM Systems Director on the management server.
Verify that the systems meet the requirements for the agents you will install.
Perform any preparation steps that are required on the managed systems.
“Importing agent packages”
Related information
IBM Systems Director Best Practices Redwiki
″Developing automation″ in the Tivoli Provisioning Manager Information
Center

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.

Use the following procedure to import one or more agent packages for distribution
using the Agent Installation Wizard.
1. Copy the package files to a directory on the management server.
2. In the IBM Systems Director navigation area, click Release Management →
Agents. The available agent package groups are listed.
3. Click Import Agent. The Import Agent window opens.
4. Type the path on the management server where you copied the package files in
step 1, and then click OK.

466 IBMSystems Director Systems Management Guide

 5. Restart the IBM Systems Director Server service.

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” on page 463
Related information
″Developing automation″ in the Tivoli Provisioning Manager Information
Center

Creating agent packages

If you need to distribute and install an agent or subagent to your managed
systems, you can create an agent package that can be distributed by the Agent
Installation Wizard.

Sample: tc-driver.xml
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE tc-driver>

<tc-driver>
<tc-driver-format>2.0</tc-driver-format>
<driver-name>PlatformAgentPackage</driver-name>
<version>5.20.3</version>
<description>This TC Driver contains the Agent Package for the
Platform Agent</description>
<documentation location="doc/package.html" />
<dependencies>
<dependency name="core" />
<dependency name="default-device-model" />
<dependency name="LocalFileRepository" />
</dependencies>
<property name="tc.pkg" location="com.thinkdynamics.kanaha.tcdrivermanager.action" />
<actions>
<action name="copy-file" class="${tc.pkg}.CopyFileActions" />
<action name="import" class="${tc.pkg}.ImportAction" />
</actions>
<items>
<item name="package/dir5.20.3_coreservices_windows.exe" action="copy-file">
<param name="dest.path"
value="${twg.directory.packages}/agent/platformagents/dir5.20.3_coreservices_windows.exe" />
</item>
<item name="package/dir5.20.3_coreservices_linux.sh" action="copy-file">
<param name="dest.path"
value="${twg.directory.packages}/agent/platformagents/dir5.20.3_coreservices_linux.sh" />
</item>
</items>
<dcm>
<item name="xml/PlatformAgentWindows_5_20_3.xml" action="import" />
<item name="xml/PlatformAgentLinux_5_20_3.xml" action="import" />
</dcm>
</tc-driver>

Chapter 9. Managing agents 467

 Sample package xml, PlatformAgentWindows_5_20_3.xml
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE datacenter PUBLIC "-//Think Dynamics//DTD XML Import//EN"
"http://www.thinkdynamics.com/dtd/xmlimport.dtd">
<!--
Create DCM SoftwareModule, SRTs and Installable objects required
by CommonAgentService_1_4
-->
<datacenter>
<software-module
name="IBM Platform Agent-5.20.2"
version="5.20.2"
vendor="IBM"
package_type=”PlatformAgent”
title="IBM Director Core Services">
<!-- Linux -->
<installable-package
name="IBM Director Core Services Linux86 Installable"
version="5.20.2"
file-repository="LocalFileRepository"
status="tested"
priority="1"
is-device-model="CAS_14_Windows_SoftwareInstallableDM">
<file
name="dir5.20.2_coreservices_linux.sh"
path="/packages/agent/Platform/Linux86" />
<software-requirement
name="platform.os.family"
type="HARDWARE">
<software-requirement-value value="Linux" />
</software-requirement>
<software-requirement
name="platform.architecture"
type="HARDWARE">
<software-requirement-value value="intel" />
</software-requirement>
</installable-package>
<!-- Windows -->
<installable-package
name="IBM Director Core Services Windows Installable"
version="5.20.2"
file-repository="LocalFileRepository"
status="tested"
priority="2"
is-device-model="CAS_14_Windows_SoftwareInstallableDM">
<file
name="dir5.20.2_coreservices_windows.exe"
path="="/packages/agent/Platform/Windows" />
<software-requirement
name="platform.os.family"
type="HARDWARE">
<software-requirement-value value="Windows" />
</software-requirement>
</installable-package>
<!-- Windows -->
<software-resource-template
name="IBM Director Core Services Windows"
software-resource-type="INSTALLATION"
software-resource-device-model="CAS_14_SoftwareInstallationDM"
is-default="true">
<software-requirement
name="platform.os.family"
type="HARDWARE">
<software-requirement-value value="Windows" />
</software-requirement>
<template-param
name="# Install Command"

468 IBMSystems Director Systems Management Guide

 value="dir5.20.2_coreservices_windows.exe -a silent"
multiplicity-type="One"
is-changeable="false" />
<!-- TODO Need to find uninstall command for platform agent -->
<template-param
name="# Uninstall Command"
value=""
multiplicity-type="One"
is-changeable="false" />
<template-param
name="# Installable Temp Directory"
value="c:\\dir_corsrv_temp"
multiplicity-type="One"/>
<template-param
name="# Remove Installable Temp Directory"
value="true"
multiplicity-type="One" >
<template-param-value value="true" is-default="true"/>
<template-param-value value="false" is-default="true"/>
</template-param>
</software-resource-template>
</software-module>
</datacenter>

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
Director Web interface.

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:
Name The globally unique identifier (GUID) of the system on which the agent
manager is installed.
IP Address
The IP address of the agent manager.
CAS Version
The common agent services version of the agent manager.
Active Whether or not the agent manager is the active agent manager for IBM
Systems Director Server.

Chapter 9. Managing agents 469

 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.

Use the following procedure to add a new agent manager:

1. Click Settings → Agent Manager Configuration.
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.

470 IBMSystems Director Systems Management Guide

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
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.

To set the active agent manager, use the following procedure:

1. Click Settings → Agent Manager Configuration.
2. In the Agent Manager Configuration page, select the agent manager you want
to delete, 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 474

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:
1. Click Settings → Agent Manager Configuration.
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.

Chapter 9. Managing agents 471

 Using a remote agent manager with IBM Systems Director
There are several reasons why you might want to use a remote agent manager
instead of the agent manager that is embedded in IBM Systems Director Server.
v If you need to manage a common agent with both IBM Systems Director Server
and a different management application, you cannot use the agent manager that
is embedded in IBM Systems Director Server.
v 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.
v If you need to configure your agent manager for high availability, you cannot
use the agent manager that is embedded in IBM Systems Director Server.
v If you need to improve performance for IBM Systems Director Server, especially
during discovery, using an agent manager that is installed on a separate server
from IBM Systems Director Server can be an effective solution.

These situations are addressed by configuring one or more of the management

applications to use a remote agent manager. In some cases, the remote agent
manager can be the lightweight runtime version of agent manager that is
embedded in IBM Systems Director Server. In other cases, a full version of agent
manager must be installed.

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.
embedded IBM WebSphere Application Server
This runtime environment might be delivered with the agent manager
installer. During the installation of the agent manager, the agent manager
installer uses a downloaded copy of the embedded version of IBM
WebSphere Application Server archive file located in one of its directories.
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.

Before beginning this procedure, ensure that you have the following information
available:
v the host name or IP address of the agent manager you will use

472 IBMSystems Director Systems Management Guide

 v the user name and password of the IBM Systems Director user that will be used
to register IBM Systems Director Server with agent manager
v the agent registration password that is used to register common agents with
agent manager
v the public communications port used by agent manager

IBM Systems IBM Systems

Director Server Director Server

Resource manager Resource manager

Embedded agent Embedded agent

manager manager

Common agents

Using an agent manager other than the agent manager that is

embedded in IBM Systems Director Server
If your management environment will use any other management applications in
addition to IBM Systems Director, if you need to configure agent manager for high
availability, or if you want to improve performance by installing agent manager on
a system without IBM Systems Director Server, you can configure IBM Systems
Director Server to use an agent manager other than the embedded one.

IBM Systems Director can use agent managers that conform to the common agent
services architecture, version 1.4 and later.

Before beginning this procedure, ensure that you have the following information
available:
v the host name or IP address of the agent manager you will use
v the user name and password of the IBM Systems Director user that will be used
to register IBM Systems Director Server with agent manager
v the agent registration password that is used to register common agents with
agent manager
v the public communications port used by agent manager

Chapter 9. Managing agents 473

IBM Systems IBM Systems
Director Server Director Server

Resource manager Resource manager

Agent 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 only by one agent manager at
a time. If that agent manager is not the agent manager that is being used by IBM
Systems Director, 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

Note: An alternative to changing the agent manager that is used by a Common

Agent is to configure IBM Systems Director Server to use the agent manager that is
used by the 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 471

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: 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

474 IBMSystems Director Systems Management Guide

 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

/opt/ibm/icc/slp/bin/slp_query
--type=service:management-software.IBM:usma --address=agent_ip
Windows

\Program Files\Common Files\IBM\ICC\slp\bin\slp_query

--type=service:management-software.IBM:usma --address=agent_ip

where agent_ip is the IP address of the Common-Agent managed system.

The agent manager is identified in the results by the string
manager=am_ip

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)

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 is being used by IBM Systems Director, you can unregister the
Common-Agent managed system with the incorrect agent manager and then
discover the Common-Agent managed system to set the agent manager to the one
that is being used by IBM Systems Director. Complete the following steps on the
Common-Agent managed system:
1. Delete the common agent certificate files. At a command prompt, type the
following command:
or Linux

rm -rf /opt/ibm/director/agent/runtime/agent/cert/*
Windows

DEL /F /S /Q install_root\agent\runtime\agent\cert\*.*

where install_root is the root directory of your IBM Systems Director

installation.
2. In a text editor, open the install_root\agent\runtime\agent\config\
endpoint.properties file for editing, 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 (/).

Chapter 9. Managing agents 475

 3. In the endpoint.properties file, find the unmanagedAgent property and set it
to true:
unmanagedAgent=true
4. In the endpoint.properties file, find and replace the IP address of the agent
manager (from “Identifying the agent manager for a Common-Agent managed
system” on page 474) with localhost.

Tip: This generally means changing each of the following lines to specify a
value of localhost:
PatchService.Host=localhost
CatalogueService.Host=localhost
CertManagement.Host=localhost
AgentQuery.Host=localhost
Registration.Server.Host=localhost
TrustedCertificateQuery.Host=localhost
AgentManagerQuery.Host=localhost
5. Save and close the endpoint.properties file.
6. Stop and restart the Common Agent by issuing the following commands:
or Linux

/opt/ibm/director/agent/runtime/agent/bin/endpoint.sh stop
/opt/ibm/director/agent/runtime/agent/bin/endpoint.sh start
Windows

install_root\agent\runtime\agent\bin\endpoint.bat stop
install_root\agent\runtime\agent\bin\endpoint.bat start

where install_root is the root directory of your IBM Systems Director

installation.
7. 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 474. The agent manager should now be unmanaged.

Registering a Common-Agent managed system with the IBM

Systems Director agent manager
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 and request access. The
Common-Agent managed system should now be managed by the agent
manager used by IBM Systems Director. To verify this, you can use the
procedure described in “Identifying the agent manager for a Common-Agent
managed system” on page 474.

Viewing the agent manager configuration

You can view the configuration of an agent manager in a Web browser.

You can also use this procedure to verify that an agent manager is running.

To view the configuration of an agent manager, use the following procedure:

Open the following address in your browser:

http://host_name:9513/AgentMgr/Info

where host_name is the address of the agent manager host.

476 IBMSystems Director Systems Management Guide

 Note: The public HTTP port of the agent manager embedded with IBM Systems
Director Server is 9513. If you are using an agent manager with a different public
HTTP port, substitute that port number.

If the agent manager is running, a Web page opens listing information about the
agent manager, including the following items:
v version
v instance ID
v server name
v ports used by the agent manager
v aliases for the root certificate, root key, agent manager certificate, and agent
manager key
v the paths and file names for the root keystore file, the root keystore password
file, the agent manager keystore file, the agent manager truststore file, and the
certificate revocation list file
v key size
v whether a secure connection is used for certificate revocation list download
v certificate revocation list time to live
v the database type and version used by agent manager

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:

1. Log on to the 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 Windows install_root\lwi\runtime\agentmanager\
bin\EncryptAMProps.bat new_password
Embedded agent manager on AIX or Linux ./install_root/lwi/runtime/agentmanager/
bin/EncryptAMProps.sh new_password

Chapter 9. Managing agents 477

 Agent manager type Command
Non-embedded agent manager on app_server_root\bin\EncryptAMProps.bat
Windows new_password
Non-embedded agent manager on AIX or ./app_server_root/bin/EncryptAMProps.sh
Linux 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.
v app_server_root is the root directory of the IBM WebSphere Application
Server installation.
On Windows, this is typically C:\Program Files\IBM\AgentManager.
On AIX or Linux, this is typically /opt/IBM/AgentManager.
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:

Agent manager type Command

Embedded agent manager on Windows
Embedded agent manager on AIX or Linux
Non-embedded agent manager on
Windows
Non-embedded agent manager on AIX or
Linux
install_root\jre\bin\ikeyman.exe
./install_root/jre/bin/ikeyman.sh
app_server_root\bin\ikeyman.exe
./app_server_root/bin/ikeyman.sh

where:
v install_root is the root directory of your IBM Systems Director Server
installation.
v app_server_root is the root directory of the IBM WebSphere Application
Server installation.
On Windows, this is typically C:\Program Files\IBM\AgentManager.
On AIX or Linux, this is typically /opt/IBM/AgentManager.
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\
com.ibm.tivoli.cas.manager\certs\
Non-embedded agent manager app_server_root\certs\

where:
v install_root is the root directory of your IBM Systems Director Server
installation.
v app_server_root is the root directory of the IBM WebSphere Application
Server installation.

478 IBMSystems Director Systems Management Guide

 On Windows, this is typically C:\Program Files\IBM\AgentManager.
On AIX or Linux, this is typically /opt/IBM/AgentManager.

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 477, 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. On any common agent where you redeployed the truststore file in 8, 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:

Agent manager type Command

Embedded agent manager on Windows
Embedded agent manager on AIX or Linux
Non-embedded agent manager on
Windows
Non-embedded agent manager on AIX or
Linux
install_root\lwi\runtime\agentmanager\
bin\EncryptPW.bat
agent_registration_password
./install_root/lwi/runtime/agentmanager/
bin/EncryptPW.sh
agent_registration_password
app_server_root\bin\EncryptPW.bat
agent_registration_password
./app_server_root/bin/EncryptPW.sh
agent_registration_password

where:
v agent_registration_password is the new agent registration password.
v install_root is the root directory of your IBM Systems Director Server
installation.

Chapter 9. Managing agents 479

 v app_server_root is the root directory of the IBM WebSphere Application
Server installation.
On Windows, this is typically C:\Program Files\IBM\AgentManager.
On AIX or Linux, this is typically /opt/IBM/AgentManager.
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 the agent manager to start using the new properties file and password.

The agent registration password is now changed throughout your deployment.

Migrating common agents to a different management server

1. Install IBM Systems Director Server on the new management server.
2. On the new management server, configure IBM Systems Director Server to use
the agent manager of the old management server.
3. On the new management server, configure IBM Systems Director Server to use
the agent manager of the new management server. The common agents that
were managed using the old agent manager will be migrated to use the new
agent manager.

480 IBMSystems Director Systems Management Guide

Chapter 10. Managing IBM BladeCenter and System x
systems
IBM Systems Director provides specific tasks that can help you manage IBM
BladeCenter products and System x systems.

Note: Task support for IBM BladeCenter products includes most blade servers,
including the following models:
v JS21
v JS22
v QS21
v QS22
For a detailed list of supported IBM BladeCenter products and blade servers, see
“Supported IBM® BladeCenter products.”
Related concepts
eLearning: Managing blade servers with IBM Systems Director

Supported IBM BladeCenter products

The IBM BladeCenter and System x Management plug-in provides support for
BladeCenter chassis and blade servers.
v IBM BladeCenter E chassis, machine type 8677
v IBM BladeCenter H chassis, machine type 8852
v IBM BladeCenter HT chassis, machine type 8740
v IBM BladeCenter HT chassis, machine type 8750
v IBM BladeCenter S chassis, machine type 8886
v IBM BladeCenter T chassis, machine type 8720
v IBM BladeCenter T chassis, machine type 8730
v HC10 blade server, machine type 7996
v HC10 blade server, machine type 7997
v HS12 blade server, machine type 8014
v HS12 blade server, machine type 8028
v HS20 blade server, machine type 7981
v HS20 blade server, machine type 8678
v HS20 blade server, machine type 8832
v HS20 blade server, machine type 8843
v HS21 blade server, machine type 7983
v HS21 XM blade server, machine type 7995
v HS21 blade server, machine type 8853
v HS22 blade server
v HS40 blade server, machine type 8839
v JS12 blade server, machine type 7998
v JS20 blade server, machine type 8842
v JS21 blade server, machine type 7988
v JS21 blade server, machine type 8844

© Copyright IBM Corp. 1999, 2009 481

 v JS22 blade server, machine type 7998
v JS23 blade server
v LS20 blade server, machine type 8850
v LS21 blade server, machine type 7971
v LS41 blade server, machine type 7972
v QS21 blade server, machine type 0792
v QS22 blade server, machine type 0793

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: Common Agent; IBM Director
Agent, version 5.10 or later; or IBM Director Core Services, version 5.10 or later
(also called Platform Agent). 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 6.1 supports in-band communication for these service
processors:
v IPMI baseboard management controller (BMC)
v Remote Supervisor Adapter
v Remote Supervisor Adapter II
v Integrated system management processor (ISMP)

Note: You can use only out-of-band communication with management modules.

482 IBMSystems Director Systems Management Guide

 Related concepts
“Out-of-band communication requirements”
“Service processors and resource types” on page 487
“Out-of-band communication and the standard TCP Command Mode protocol” on
page 485
Related tasks
Preparing to manage service processors with IBM Systems Director
Installing IBM Systems Director
Related reference
“Out-of-band alert-forwarding strategies” on page 487

Out-of-band communication requirements

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
static 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
following documentation:
– Remote Supervisor Adapter Installation Guide at www.ibm.com/systems/
support/supportsite.wss/docdisplay?lndocid=MIGR-4ZVQKY
&brandind=5000008
– Remote Supervisor Adapter II Installation Guide at www.ibm.com/systems/
support/supportsite.wss/docdisplay?lndocid=MIGR-57090
&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
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

Chapter 10. Managing IBM BladeCenter and System x systems 483

 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 using an
interconnect gateway.

The following table lists the pathways that are available for out-of-band
communication:
Table 27. 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
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 Remote Supervisor Adapter II
v Management module
v Advanced management module
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. Only one of the following systems management applications can communicate
with a service processor at any given time:
v IBM Systems Director Server
v IBM® Management Process Command-Line Interface (MPCLI) (also called
IBM® Hardware Command-Line Interface)
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 with the
RXE-100 Remote Expansion Enclosure. If you have one of the following servers

484 IBMSystems Director Systems Management Guide

 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
“In-band communication requirements” on page 482
“Service processors and resource types” on page 487
Related reference
“Out-of-band alert-forwarding strategies” on page 487
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 Advanced management module
v Remote Supervisor Adapter
v Remote Supervisor Adapter II
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 IBM® Management Process Command-Line Interface (MPCLI)
v UpdateXpress
v Cluster Systems Management
v Active Energy Manager (Standalone edition)
By default, service processors and management modules are enabled to use the
standard TCP Command Mode protocol. However, service processors and
management modules permit only one connection at a time when using the
standard TCP Command Mode protocol. If a system is communicating with
another IBM® program that uses the standard TCP Command Mode protocol, IBM
Systems Director Server cannot communicate with that system.

When IBM Systems Director Server cannot communicate with the service processor
or management module, you might have problems with that system, for example:
v Access requests fail

Chapter 10. Managing IBM BladeCenter and System x systems 485

 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.

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 will attempt 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 will use the
standard TCP Command Mode protocol.

To change the preference of using the secure TCP Command Mode protocol first,
complete the following steps:
1. Navigate to the install_root/lwi/runtime/data/asmDefinitions.properties file,
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 (/).
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 into the

486 IBMSystems Director Systems Management Guide

 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.

Out-of-band alert-forwarding strategies

System x and xSeries service processor 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 28. Out-of-band alert-forwarding strategies
Type of service processor Possible alert-forwarding strategies
Intelligent Peripheral Management Interface IBM Systems Director comprehensive
(IPMI) baseboard management controller
(BMC)
Integrated system management processor Not applicable
(ISMP)
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)

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
“In-band communication requirements” on page 482
“Out-of-band communication requirements” on page 483
“Service processors and resource types”

Service processors and resource types

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

Chapter 10. Managing IBM BladeCenter and System x systems 487

 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 v BladeCenter chassis

v Advanced management module v Blade server
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 Remote Supervisor Adapter
v Remote Supervisor Adapter II

Related concepts
“In-band communication requirements” on page 482
“Out-of-band communication requirements” on page 483
Related reference
“Out-of-band alert-forwarding strategies” on page 487

Viewing the IBM BladeCenter and System x management summary

You can view a summary of all management and configuration activity that is
associated with IBM BladeCenter products and x86-based and x64-based System x
servers, including the number of systems that have been discovered, have
problems, and require updates. It also provides information about required I/O
module plug-ins. Note that information on this page is refreshed automatically
when there are any changes.

To view the summary, complete the following steps:

1. In the IBM Systems Director navigation area, click Welcome.
2. Click the Manage tab.
3. On the Manage page, scroll to the IBM BladeCenter and System x section of
the page and click the IBM BladeCenter and System x Management section
heading. The IBM BladeCenter and System x management summary is
displayed.
4. View the Management section. This section provides the following information:
v The number of IBM BladeCenter chassis or blade servers that have problems,
the number of IBM BladeCenter resources that are not in compliance, the
number of System x servers or service processors that have problems, and
the number of System x resources that are not in compliance.

Note: You can click any of these links to display a list of the affected IBM
BladeCenter or System x products.
v In the Common tasks area, the following links are provided:
System discovery
Click to discover systems and specific types of resources in your
network.
488 IBMSystems Director Systems Management Guide
 View servers and service processors
Click to display the servers and service processors that have been
discovered in your systems-management environment. If a server has
Common Agent or Platform Agent installed, the server is displayed.
Otherwise, IBM Systems Director must use out-of-band
communication with the service processor and the service processor
is displayed.
View monitors and set thresholds
Click to open the Monitors task. On this page, you can select a
system or group to monitor and then select a view to show. Create
your own view to group monitors of your choice.
View and collect inventory
Click to open the View and Collect Inventory task. On this page, you
can collect the most current inventory from a resource or view the
inventory of a resource.
Check for updates
Click to open the Check for Updates page. On this page, you can
select the updates you want to check.
5. View the BladeCenter Additional Configuration Plug-in Setup section. This
section provides the following information:
v A pie chart and corresponding list that indicates the number of I/O module
plug-ins in each of the following groups:
– Required
– Not installed
– Installed, but have errors
– Installed, but require activation
– Active

Note: You can click any of these links to display a list of the affected
I/O-module plug-ins.
v In the Common tasks area, the following links are provided:
View I/O module plug-ins
Click to open the I/O Module Plug-ins page that lists the available
I/O-module vendor plug-ins and indicates whether any of the
plug-ins are required before you can configure the IBM BladeCenter
chassis in your environment. If a plug-in is required and is not
installed, this page directs you to the Web page from which you can
download it.
View blade servers and chassis
Click to display the blade servers, switches, and chassis that have
been discovered in your systems-management environment.
6. View the Configuration section. This section provides the following
information:
v Information about any configuration plans that have been created and set as
detect-apply plans for BladeCenter or System x systems.
v In the Common tasks area, the following links are provided:
Configuration plans
Click to view available configuration plans that you can use to
configure hardware and operating systems.

Chapter 10. Managing IBM BladeCenter and System x systems 489

 Templates
Click to view configuration templates that store device parameters
and settings for IBM BladeCenter chassis.

You also can reach the summary page by using Find a Task. For more information,
see “Finding a task.”
Related concepts
eLearning: Managing blade servers with IBM Systems Director

Downloading and activating BladeCenter I/O module plug-ins

IBM Systems Director identifies BladeCenter I/O modules in your
systems-management environment. You can download and activate the plug-ins for
the identified I/O modules.

To download and activate I/O module plug-ins, complete the following steps:
1. In the IBM Systems Director navigation area, click Welcome.
2. Click the Manage tab.
3. On the Manage page, scroll to the IBM BladeCenter and System x section of
the page and click the IBM BladeCenter and System x Management section
heading. The IBM BladeCenter and System x 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 Web site opens in a new window.
7. Locate and download the I/O module plug-ins that are required.
8. Click Scan and Activate Plug-ins. IBM Systems Director scans the downloaded
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.

490 IBMSystems Director Systems Management Guide

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.

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 workaround support.

The following table lists configuration tasks that IBM Systems Director version
6.1.1 does not support for integrated management modules. The table also observes
alternate ways to provide the support to integrated management modules.
Table 29. Affected configuration tasks and available workaround support
Affected configuration tasks Workaround support
SNMP configuration in configuration Configure SNMP using the IBM
manager management-module Web interface
SMTP configuration in configuration Configure SMTP using the IBM
manager management-module Web interface
IP configuration in configuration manager Configure the specific IP setting using the
does not support the setting Try DHCP and IBM management-module Web interface
if that fails use static address
Ports configuration in configuration manager Configure ports using the IBM
does not provide network port reassignment management-module Web interface
settings
Enhanced user login security configuration Configure security using the IBM
is not provided in configuration manager management-module Web interface

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.

Management Processor Command Line Interface support

Management Processor Command Line Interface (MPCLI) is not supported on

systems with integrated management modules. The following systems are affected:
v iDataPlex™, machine types 7321 and 7323
v System x3400M2, machine types 7836 and 7837
v System x3550M2, machine type 7946
v System x3650M2, machine type 7947
v HS22 blade server, machine type 7870

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 using IBM Systems Director.

To change the IP address, complete the following steps:

Chapter 10. Managing IBM BladeCenter and System x systems 491

 1. Discover the integrated management module by specifying its IP address. For
detailed information about discovery, see “Discovering systems with system
discovery.” A Server resource is displayed in the IBM Systems Director IBM
Systems Director Web interface.
2. Request access to the Server resource.
3. 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.”
4. Apply the template to the applicable Server resource.

The Server resource loses connectivity, but will go online using the new IP address.
Related tasks
“Configuring the network IP for a System x service processor” on page 537

Changing the integrated management module IP address by

way of the System resource
You can change the integrated management module IP address by way of the
System resource using IBM Systems Director.

To change the IP address, complete the following steps:

1. Discover the system containing the integrated management module by
specifying the system IP address For detailed information about discovery, see
“Discovering systems with system discovery.” A System resource is displayed
in the IBM Systems Director IBM Systems Director Web interface.
2. Request access to the System resource.
3. 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.”
4. Apply the template to the applicable System resource.

The Server resource will go online using the new IP address.

Changing the network port on an integrated management

module
You can change the network port on an integrated management module using IBM
Systems Director and the IBM integrated-management-module Web interface.

To change the network port, complete the following steps:

1. Discover the integrated management module by specifying its IP address. For
detailed information about discovery, see “Discovering systems with system
discovery.” A Server resource is displayed in the IBM Systems Director IBM
Systems Director Web interface.
2. Start the IBM integrated-management-module Web interface using the
integrated management module IP address.
3. Log into the integrated management module.
4. Change the applicable network port settings.
5. Restart the system containing the integrated management module for the
settings to take effect.

The Server resource loses connectivity due to the system restart. When the system
is online again, the Server resource uses the new port.

492 IBMSystems Director Systems Management Guide

Configuring integrated management module security
You can configure security for an integrated management module using the IBM
integrated-management-module Web interface.

To configure security, complete the following steps:

1. Start the IBM integrated-management-module Web interface using the
integrated management module IP address.
2. Log into the integrated management module.
3. 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 using IBM Systems Director and the IBM
integrated-management-module Web interface.

To configure security, complete the following steps:

1. Discover the integrated management module by specifying its IP address. For
detailed information about discovery, see “Discovering systems with system
discovery.” A Server resource is displayed in the IBM Systems Director IBM
Systems Director Web interface.
2. Start the IBM integrated-management-module Web interface using the
integrated management module IP address.
3. Log into the integrated management module.
4. Configure the Try DHCP, and if that fails use static IP setting.
5. Restart the system containing the integrated management module for the
settings to take effect.

The Server resource loses connectivity due to the system restart. When the system
is online again, the Server resource uses the new IP address.

Enabling Secure Sockets Layer after discovery

You can enable Secure Sockets Layer (SSL) for the integrated management module
after discovering the resource in IBM Systems Director.

To enable SSL, complete the following steps:

1. Discover the integrated management module by specifying its IP address. For
detailed information about discovery, see “Discovering systems with system
discovery.” A Server resource is displayed in the IBM Systems Director IBM
Systems Director Web interface.
2. Request access to the integrated management module. IBM Systems Director
communicates with the integrated management module using unsecured
sockets layer.
3. Start the IBM integrated-management-module Web interface using the
integrated management module IP address.
4. Log into the integrated management module.
5. Enable SSL and generate a self-signed certificate.
6. Restart the system containing the integrated management module for the
settings to take effect.

Chapter 10. Managing IBM BladeCenter and System x systems 493

 IBM Systems Director communicates with the integrated management module
using SSL.

Enabling Secure Sockets Layer before discovery

You can enable Secure Sockets Layer (SSL) for the integrated management module
before discovering the resource in IBM Systems Director.

To enable SSL, complete the following steps:

1. Start the IBM integrated-management-module Web interface using the
integrated management module IP address.
2. Log into the integrated management module.
3. Enable SSL and generate a self-signed certificate.
4. Restart the system containing the integrated management module for the
settings to take effect.
5. Discover the integrated management module by specifying its IP address. For
detailed information about discovery, see “Discovering systems with system
discovery.” A Server resource is displayed in the IBM Systems Director IBM
Systems Director Web interface.
6. Request access to the integrated management module.

IBM Systems Director communicates with the integrated management module

using SSL.

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.

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:

1. In the IBM Systems Director Web interface navigation area, click Navigate
Resources.
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.

494 IBMSystems Director Systems Management Guide

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

The Remote Supervisor Adapter, Remote Supervisor Adapter II, and Intelligent
Platform Management Interface (IPMI) baseboard management controller (BMC)
service processors installed in IBM® System x servers, including scalable servers,
provide support for Power On/Off using out-of-band communication.

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. Subsequently 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 Shut Down and Power Off.
Table 30. Service processor support for power settings
Service processor Power settings supported
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
IPMI baseboard management controllers in Power On, Restart Now, and Power Off
servers that are not blade servers Now
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.”

Chapter 10. Managing IBM BladeCenter and System x systems 495

 Related concepts
“Out-of-band communication requirements” on page 483
“Power On/Off task support using Wake on LAN technology on System x”
“Power On/Off task support by way of the operating system on System x and
blade servers”
Related tasks
“Changing the power state on System x and IBM BladeCenter hardware” on page
497

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
“Power On/Off task support using out-of-band communication” on page 495
“Power On/Off task support by way of the operating system on System x and
blade servers”
Related tasks
“Changing the power state on System x and IBM BladeCenter hardware” on page
497

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.

496 IBMSystems Director Systems Management Guide

 See the following table for more information.
Table 31. Power-state-setting support by operating systems running on System x servers;
IBM® and third-party x86-based systems
Operating system Power settings supported
Windows (32-bit and 64-bit versions) Restart and Shutdown
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)

Related concepts
“Power On/Off task support using out-of-band communication” on page 495
“Power On/Off task support using Wake on LAN technology on System x” on
page 496
Related tasks
“Changing the power state on System x and IBM BladeCenter hardware”

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 “Requesting access to a secured system.”

To change the power state, complete the following steps:

1. In the IBM Systems Director Web interface navigation area, click Navigate
Resources.
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 you
want to invoke. 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 Run window, click OK to change the power state immediately. You also
can schedule this task to run at a later time. For more information, see
“Scheduling tasks.”

Chapter 10. Managing IBM BladeCenter and System x systems 497

 Related concepts
“Power On/Off task support using out-of-band communication” on page 495
“Out-of-band communication requirements” on page 483
“Power On/Off task support using Wake on LAN technology on System x” on
page 496
“Power On/Off task support by way of the operating system on System x and
blade servers” on page 496

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 519 for detailed
steps for configuring SNMPv1 and SNMPv3 settings.
Table 32. 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 IBM Systems Director Server
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.

498 IBMSystems Director Systems Management Guide

 Related tasks
“Configuring SNMP options for an IBM BladeCenter management module” on
page 519
“Specifying SNMPv1 options for an IBM BladeCenter management module” on
page 519
“Specifying SNMPv3 options for an IBM BladeCenter management module” on
page 521

Using hardware-log information from System x service processors and

IBM BladeCenter products
System x service processors and IBM BladeCenter management modules and
service processors provide hardware logs. 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. You can view and clear hardware-log
information using the IBM Systems Director Web interface.

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 Remote Supervisor Adapter II
v Remote Supervisor Adapter
v Management module
v Advanced management module
The following table details the available hardware-log access paths for the service
processors and management modules.
Table 33. 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 the blade server v Out-of-band communication with the service processor using the
management module or advanced management module
v In-band communication with the service processor using Common Agent
or Platform Agent installed on the blade server
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.”

Chapter 10. Managing IBM BladeCenter and System x systems 499

 Related concepts
“In-band communication requirements” on page 482
“Out-of-band communication requirements” on page 483
Related tasks
“Viewing hardware-log information”
“Refreshing hardware-log information” on page 501
“Clearing the hardware-log information” on page 501
“Providing hardware-log information” on page 502

Viewing hardware-log information

The Hardware Log page displays information generated by service processors in
System x servers and by management modules and service processors in
BladeCenter 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.”

500 IBMSystems Director Systems Management Guide

 v Export the information. For more information, see “Exporting table information.”
Related concepts
“Hardware-log information using out-of-band and in-band communication” on
page 499
“In-band communication requirements” on page 482
“Out-of-band communication requirements” on page 483
Related tasks
“Refreshing hardware-log information”
“Clearing the hardware-log information”
“Providing hardware-log information” on page 502

Refreshing hardware-log information

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
“Hardware-log information using out-of-band and in-band communication” on
page 499
“In-band communication requirements” on page 482
“Out-of-band communication requirements” on page 483
Related tasks
“Viewing hardware-log information” on page 500
“Clearing the hardware-log information”
“Providing hardware-log information” on page 502

Clearing the hardware-log information

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.

Chapter 10. Managing IBM BladeCenter and System x systems 501

 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 Clear to confirm the request. The
hardware-log information is cleared from the table and from the service
processor or management module.
Related concepts
“Hardware-log information using out-of-band and in-band communication” on
page 499
“In-band communication requirements” on page 482
“Out-of-band communication requirements” on page 483
Related tasks
“Viewing hardware-log information” on page 500
“Refreshing hardware-log information” on page 501
“Providing hardware-log information”

Providing hardware-log information

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.

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.

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.

502 IBMSystems Director Systems Management Guide

 Option Description
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.
5. In the file download window for your Web browser, click Save to Disk and
then click OK.
6. 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.
Related concepts
“Hardware-log information using out-of-band and in-band communication” on
page 499
“In-band communication requirements” on page 482
“Out-of-band communication requirements” on page 483
Related tasks
“Viewing hardware-log information” on page 500
“Refreshing hardware-log information” on page 501
“Clearing the hardware-log information” on page 501

Using locator LED settings on IBM BladeCenter and System x servers

System x servers and BladeCenter products 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 the IBM Systems Director Web interface.

Locator LEDs and out-of-band and in-band communication

System x servers and BladeCenter products provide a hardware feature called the
locator LED. Support is provided using either out-of-band and in-band
communication.

Support for changing the locator-LED setting is provided by the following System
x and BladeCenter 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 Supervisor Adapter
v Remote Supervisor Adapter II
v Remote I/O enclosure
v Management module
v Advanced management module

Chapter 10. Managing IBM BladeCenter and System x systems 503

 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
“In-band communication requirements” on page 482
“Out-of-band communication requirements” on page 483
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 the
locator LED on or off 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:

1. In the IBM Systems Director Web interface navigation area, click Navigate
Resources.
2. Navigate to the system on which you want to change the locator-LED setting.
3. View the Access column to make sure that you can access the system. If Access
is set to None, you must request access to the system.
4. Right-click the system and click 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 at a later time. For more information, see
“Scheduling tasks.”
Related concepts
“Locator LEDs and out-of-band and in-band communication” on page 503
“In-band communication requirements” on page 482
“Out-of-band communication requirements” on page 483

Solving hardware problems using light-path-diagnostic LEDs on IBM

BladeCenter and System x servers
System x servers and BladeCenter products provide a hardware feature called the
light-path-diagnostic LED. These LEDs are located on the front of System x servers,
on the server rear panel, on light path adapters, on field replaceable units (FRUs),
on planars, on BladeCenter chassis, and on blade servers. A server or chassis can
have LEDs associated with the processor, memory, power supply, fan, and more.
Each LED can indicate whether its associated component is having problems or
has failed. For information about what light-path-diagnostics LEDs are available on
your System x or BladeCenter hardware, see the hardware documentation. You can
view the light-path-diagnostic LED settings using the IBM Systems Director Web
interface.

504 IBMSystems Director Systems Management Guide

Light-path-diagnostic LED information
Light-path-diagnostic LED information consists of the LED name and severity, its
state, color, and location. For information about what light-path-diagnostics LEDs
are available on your System x or BladeCenter 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 34. LED name and associated severity
LED name Severity
Activity OK
CPU Critical
CPU x Critical

where x indicates a number from 1 to 8.

CPU mismatch Critical
DASD Critical
DASD x Critical

where x indicates a number from 1 to 2.

DIMM Critical
DIMM x Critical

where x indicates a number from 1 to 16.

Diagnostic card Critical
Fan Critical
Fan x Critical

where x indicates a number from 1 to 16.

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

where x indicates a number from 1 to 5.

POST OK Informational
PS Critical

Chapter 10. Managing IBM BladeCenter and System x systems 505

 Table 34. LED name and associated severity (continued)
LED name Severity
PS x Critical

where x indicates a number from 1 to 4.

Select CD OK
Select KVM OK
Service Processor Critical
VRM Critical
VRM x Critical

where x indicates a number from 1 to 8.

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 34 on page 505).

LEDs can have the following colors:

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 (Setting light-path-diagnostic LED settings)

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:

506 IBMSystems Director Systems Management Guide

 1. Navigate to your system in Navigate Resources, 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.

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 Navigate Resources, 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 →
Light-path-diagnostic LEDs.

Note: If the selected resource does not support light-path-diagnostic LEDs or

there is a problem communicating with the resource to obtain the LED state,
the Light-path-diagnostic LEDs task is not displayed.
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, select the affected
LED and 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

Chapter 10. Managing IBM BladeCenter and System x systems 507

 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.

Configuring templates
You can configure templates for use in the Configuration Manager task. These
templates can configure IBM BladeCenter products and System x servers.
Related tasks
Chapter 4, “Configuring systems,” on page 267

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.

508 IBMSystems Director Systems Management Guide

 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.

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

Chapter 10. Managing IBM BladeCenter and System x systems 509

 Security fields Legacy Security Settings High Security Settings
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.

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 System x service processor” on page 536
“Configuring security levels for an IBM BladeCenter management module” on
page 515

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 this template for BladeCenter installations that include management
modules or advanced management modules. The settings provided by this
template 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 template.
2. On the Templates page, click Create Template.
3. In the Create Template window, select an appropriate target chassis from the
Template type list.

510 IBMSystems Director Systems Management Guide

 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.

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 this template for BladeCenter installations that include
management modules or advanced management modules. The settings provided
by this template 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.

Chapter 10. Managing IBM BladeCenter and System x systems 511

 To create a new account of a user of the management module, complete the
following steps:
1. On the Configuration manager summary page, locate the Configuration tasks
section and click Create a template.
2. On the Templates page, click Create Template.
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 Management Module
Login 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 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.

512 IBMSystems Director Systems Management Guide

 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.
21. Optional: To return to the Templates page, click Cancel.
Related tasks
“Modifying an existing account for the IBM BladeCenter management module”
“Deleting an account for a IBM BladeCenter management module” on page 514

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:
1. On the Configuration manager summary page, locate the Configuration tasks
section and click Create a template.
2. On the Templates page, click Create Template.
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 Management Module
Login Configuration.
5. Type a name in the Configuration template name field.
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.
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 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 Alphanumeric characters only
v 5 - 15 characters
v At least 1 alphabetic character
v At least 1 numeric character
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.

Chapter 10. Managing IBM BladeCenter and System x systems 513

 Read-only
The user cannot change any information on the management module.
16. 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.
17. Select the tasks (including the task that you just created) that you want to run.
18. 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.
19. To return to the Templates page, click Cancel.
Related tasks
“Creating a new account for the IBM BladeCenter management module” on page
511
“Deleting an account for a IBM BladeCenter management module”

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:
1. On the Configuration manager summary page, locate the Configuration tasks
section and click Create a template.
2. On the Templates page, click Create Template.
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 Management Module
Login Configuration.
5. Type a name in the Configuration template name field.
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.
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 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.
13. Click OK. The Management Module Login Configuration page is displayed
with the new task.

514 IBMSystems Director Systems Management Guide

 Important: You must complete the following steps in this procedure or the
task will not run.
14. Select the tasks (including the task that you just created) that you want to run.
15. 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.
16. To return to the Templates page, click Cancel.
Related tasks
“Creating a new account for the IBM BladeCenter management module” on page
511
“Modifying an existing account for the IBM BladeCenter management module” on
page 513

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:
1. On the Configuration manager summary page, locate the Configuration tasks
section and click Create a template.
2. On the Templates page, click Create Template.
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 Management Module
Security Level 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 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.

Chapter 10. Managing IBM BladeCenter and System x systems 515

 Important: If you close this page without clicking Save, no changes are made
to the template and the information that you entered is lost.
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
No selection has been made. If you save with this selection, the
Default-account-password expiration on first access property is not
applied.

516 IBMSystems Director Systems Management Guide

 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
No selection has been made. If you save with this selection, the
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.
22. 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.
23. Optional: To return to the Templates page, click Cancel.
Related concepts
“Password security levels for IBM BladeCenter management modules and System
x service processors” on page 508

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.

Note: You can use this template for BladeCenter installations that include
management modules or advanced management modules. The settings provided
by this template 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 specify the network IP for an IBM BladeCenter management module, complete

the following steps:
1. On the Configuration manager summary page, locate the Configuration tasks
section and click Create a template.
2. On the Templates page, click Create Template.

Chapter 10. Managing IBM BladeCenter and System x systems 517

 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 Management Module
Network IP 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 Management Module Network IP Configuration page is
displayed with two tabs: IP Configuration and DNS Configuration.
9. On the IP Configuration page, select your DHCP setting from the DHCP list.
nothing selected
No action is performed with regards to DHCP settings.
Activate
DHCP is activated.
Deactivate
DHCP is deactivated, that is, the DHCP function will not be used. The
management module will use a static IP address.
If DHCP fails, use static IP configuration
If DHCP is used and fails while running, use the provided static IP
address information provided.
10. 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.”
11. If you selected Get an IP address from the IP address pool, select an IP
address pool template.
12. If you selected Use the specified IP address, type the IP address, gateway,
and subnet mask.

Note: IPv4 addresses are accepted.

13. Click the DNS Configuration tab.
14. Select whether you want to activate or deactivate the full name (DNS) setting
from the DNS list.
15. Type the DNS-server IP addresses in the DNS-server IP address fields 1, 2,
and 3.

Note: IPv4 addresses are accepted.

16. Click Save to save the changes in the configuration template. If you are
updating the configuration in real time, click Deploy.
Attention: 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.
17. Optional: To return to the Templates page, click Cancel.

518 IBMSystems Director Systems Management Guide

Related tasks
“Configuring the IP address pool for IBM BladeCenter systems and System x
servers” on page 532

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.

Note: You can use this template for BladeCenter installations that include
management modules or advanced management modules. The settings provided
by this template 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 specify the SNMPv1 and SNMPv3 protocols for the management module,
complete the following steps:
1. On the Configuration manager summary page, locate the Configuration tasks
section and click Create a template.
2. On the Templates page, click Create Template.
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 Management Module
Network SNMP 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 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”
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”
on page 498

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.

Chapter 10. Managing IBM BladeCenter and System x systems 519

 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
Nothing is configured if this field is left blank.
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.

Note: IPv4 addresses are accepted.

11. Type the value for the trap IP address or host name 2.
12. Type the value for the trap IP address or host name 3.
13. Click OK to record the changes in the SNMP communities table.
14. In the table, select the community that you created.
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 the page without making a selection and clicking
Save, no changes are made to the template and the information that you
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.
17. Optional: To return to the Templates page, click Cancel.

520 IBMSystems Director Systems Management Guide

Related tasks
“Specifying SNMPv3 options for an IBM BladeCenter management module”
“Enabling collection of SNMP-based inventory by way of management modules”
on page 498

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.
2. Select an SNMPv3 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. Select the trap state:
nothing-selected
Nothing is configured if this field is left blank.
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. 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.
5. 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.
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

Chapter 10. Managing IBM BladeCenter and System x systems 521

 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.

Note: IPv4 addresses are accepted.

10. 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 the page without making a selection and clicking
Save, no changes are made to the template and the information that you
entered is lost.
11. Optional: To return to the Templates page, click Cancel.
Related tasks
“Specifying SNMPv1 options for an IBM BladeCenter management module” on
page 519
“Enabling collection of SNMP-based inventory by way of management modules”
on page 498

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.

You can use this template for BladeCenter installations that include management
modules or advanced management modules. The settings provided by this
template 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. While management modules and
advanced management modules support a number of ports, they support the
configuration of only some of these ports.
Table 35. Ports supported for configuration
Management
Port module Advanced management module
FTP No Yes
FTP data No Yes
HTTP Yes Yes
HTTPS Yes Yes

522 IBMSystems Director Systems Management Guide

Table 35. Ports supported for configuration (continued)
Management
Port module Advanced management module
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)

No (firmware version BPET42D and later)

Remote KVM No Yes (firmware version BPET36M and earlier)

No (firmware version BPET42D and later)

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)

No (firmware version BPET42D and later)

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:
1. On the Configuration manager summary page, locate the Configuration tasks
section and click Create a template.
2. On the Templates page, click Create Template.
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 Management Module
Ports 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 Management Module Ports Configuration page is
displayed. On this page, the current port number for each network service is
displayed.

Chapter 10. Managing IBM BladeCenter and System x systems 523

 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.
12. Click Save to save the changes in the configuration template. If you are
updating the configuration in real time, click Deploy.
13. Optional: To return to the Templates page, click Cancel.
Related concepts
“Out-of-band communication and the standard TCP Command Mode protocol” on
page 485

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.

524 IBMSystems Director Systems Management Guide

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 IBM BladeCenter management module”
“Configuring alert recipients for an IBM BladeCenter management module” on
page 527
“Deleting alert recipients for an IBM BladeCenter management module” on page
528

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.

You can use this template for BladeCenter installations that include management
modules or advanced management modules. The settings provided by this
template 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.

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.

Chapter 10. Managing IBM BladeCenter and System x systems 525

 To specify alert settings, complete the following steps:
1. On the Configuration manager summary page, locate the Configuration tasks
section and click Create a template.
2. On the Templates page, click Create Template.
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 Management Module
Alert Settings.
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 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.
14. 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.
15. Optional: To return to the Templates page, click Cancel.

526 IBMSystems Director Systems Management Guide

Related concepts
“Alert settings and recipients for an IBM BladeCenter management module” on
page 524
Related tasks
“Configuring alert recipients for an IBM BladeCenter management module”
“Deleting alert recipients for an IBM BladeCenter management module” on page
528

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.

You can use this template for BladeCenter installations that include management
modules or advanced management modules. The settings provided by this
template 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.

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:

1. On the Configuration manager summary page, locate the Configuration tasks
section and click Create a template.
2. On the Templates page, click Create Template.
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 Management Module
Alert Recipient.
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 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.

Chapter 10. Managing IBM BladeCenter and System x systems 527

 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.

Note: IPv4 addresses are accepted.

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.
17. 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.
18. Optional: To return to the Templates page, click Cancel.
Related concepts
“Alert settings and recipients for an IBM BladeCenter management module” on
page 524
Related tasks
“Configuring alert settings for an IBM BladeCenter management module” on page
525
“Deleting alert recipients for an IBM BladeCenter management module”

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:
1. On the Configuration manager summary page, locate the Configuration tasks
section and click Create a template.
2. On the Templates page, click Create Template.
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 Management Module
Alert Recipient.
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 Management Module Alert Recipient page is displayed.
9. Select the alert recipient that you want to delete.
10. Click Delete.

528 IBMSystems Director Systems Management Guide

 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.
17. 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.
18. To return to the Templates page, click Cancel.
Related concepts
“Alert settings and recipients for an IBM BladeCenter management module” on
page 524
Related tasks
“Configuring alert settings for an IBM BladeCenter management module” on page
525
“Configuring alert recipients for an IBM BladeCenter management module” on
page 527

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:
1. On the Configuration manager summary page, locate the Configuration tasks
section and click Create a template.
2. On the Templates page, click Create Template.
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 Management Network
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 Management Network Configuration page is displayed.
9. Type the VLAN ID.

Chapter 10. Managing IBM BladeCenter and System x systems 529

 10. Type the Blade System Management Processor (BSMP) IP address range
(Starting IP address).

Note: IPv4 addresses are accepted.

11. Click Create. The NIC configuration 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:
nothing selected
No action is performed with regards to DHCP settings.
Activate
DHCP is activated.
Deactivate
DHCP is deactivated, that is, the DHCP function will not be used. The
management module will use a static IP address.
If DHCP fails, use static IP configuration
If DHCP is used and fails while running, use the provided static IP
address information provided.
20. 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.”
21. If you selected Get an IP address from the IP address pool, select an IP
address pool template.
22. If you selected Use the specified IP address, type the IP address, gateway,
and subnet mask.

Note: IPv4 addresses are accepted.

23. Click OK. The Management Network Configuration page is displayed with
the new entry in the table.
24. 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 the page without making a selection and clicking
Save, no changes are made to the template and the information that you
entered is lost.
25. Optional: To return to the Templates page, click Cancel.

530 IBMSystems Director Systems Management Guide

 Related tasks
“Configuring the IP address pool for IBM BladeCenter systems and System x
servers” on page 532

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.

To configure the SNMP agent community information, complete the following

steps:
1. On the Configuration manager summary page, locate the Configuration tasks
section and click Create a template.
2. On the Templates page, click Create Template.
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.
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 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.
15. In the table, select the community that you created.
16. 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 the page without making a selection and clicking
Save, no changes are made to the template and the information that you
entered is lost.
17. Optional: To return to the Templates page, click Cancel.

Chapter 10. Managing IBM BladeCenter and System x systems 531

 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:

1. On the Configuration manager summary page, locate the Configuration tasks
section and click Create a template.
2. On the Templates page, click Create Template.
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 Pool Configuration.
5. Type a name in the Configuration template name field.
6. Optional: Type a description in the Configuration template description field.
7. Click Continue. The IP Pool Configuration page is displayed.
8. Type the Gateway address in the Gateway field.
9. Type the Subnet mask in the Subnet mask field.
10. Select the IP address add option:
Single IP address
Specifies the IP address to add to the IP address pool.
Range of IP addresses
Specifies the starting and ending IP addresses for a range of IP
addresses to add to the IP address pool.

Note: IPv4 addresses are accepted.

11. Click Add to record your selection in the IP address list.
12. 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.
13. Optional: To reset the IP address list to the values that it had when the IP
Pool Configuration page was first displayed, click Reset.
14. 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.

532 IBMSystems Director Systems Management Guide

 Related tasks
“Configuring the network IP for an IBM BladeCenter management module” on
page 517
“Configuring network resources for IBM BladeCenter blade servers” on page 529
“Configuring the network IP for a System x service processor” on page 537
“Configuring network adapters” on page 551
“Configuring IBM BladeCenter switch module protocols” on page 545

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 Remote Supervisor Adapter
v Remote Supervisor Adapter II
v Baseboard management controller (BMC)
This template is supported for scalable system partitions also.

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.

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:
1. On the Configuration manager summary page, locate the Configuration tasks
section and click Create a template.
2. On the Templates page, click Create Template.
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 Service Processor Login
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 Service Processor Login Configuration page is displayed.
9. Click Create Task. The Create Service Processor Login window is displayed.

Chapter 10. Managing IBM BladeCenter and System x systems 533

 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 Alphanumeric characters only
v 5 - 15 characters
v At least 1 alphabetic character
v At least 1 numeric character
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.

Important: You must complete the following steps in this procedure or the
task will not be run.
16. Select the tasks (including the task that you just created) that you want to 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.

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.
18. Optional: To return to the Templates page, click Cancel.
Related tasks
“Modifying an existing account for a System x service processor”
“Deleting an account for a System x service processor” on page 535

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:
1. On the Configuration manager summary page, locate the Configuration tasks
section and click Create a template.
2. On the Templates page, click Create Template.
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 Service Processor Login
Configuration.
5. Type a name in the Configuration template name field.
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.
534 IBMSystems Director Systems Management Guide
 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 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 Alphanumeric characters only
v 5 - 15 characters
v At least 1 alphabetic character
v At least 1 numeric character
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.
15. Click OK. The Service Processor Login Configuration page is displayed with
the new task.

Important: You must complete the following steps in this procedure or the
task will not be run.
16. Select the tasks (including the task that you just created) that you want to run.
17. 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.
18. To return to the Templates page, click Cancel.
Related tasks
“Creating a new account for a System x service processor” on page 533
“Deleting an account for a System x service processor”

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:
1. On the Configuration manager summary page, locate the Configuration tasks
section and click Create a template.
2. On the Templates page, click Create Template.
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 Service Processor Login
Configuration.
5. Type a name in the Configuration template name field.
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.

Chapter 10. Managing IBM BladeCenter and System x systems 535

 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 Delete Account.
11. Type the user name of the account to be deleted.
12. Click OK. The Service Processor Login Configuration page is displayed with
the new task.

Important: You must complete the following steps in this procedure or the
task will not be run.
13. Select the tasks (including the task that you just created) that you want to run.
14. 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.
15. To return to the Templates page, click Cancel.
Related tasks
“Creating a new account for a System x service processor” on page 533
“Modifying an existing account for a System x service processor” on page 534

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
server. All settings might not be applicable for the supported components.

To specify the security level for a service processor, complete the following steps:
1. On the Configuration manager summary page, locate the Configuration tasks
section and click Create a template.
2. On the Templates page, click Create Template.
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 Service Processor
Security Level 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 Service Processor Security Level Configuration page is
displayed.

536 IBMSystems Director Systems Management Guide

 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.

Important: If you close this page without clicking Save, no changes are made
to the template and the information that you entered is lost.
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
No selection has been made. If you save with this selection, the
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.
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 concepts
“Password security levels for IBM BladeCenter management modules and System
x service processors” on page 508

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.

Note: You can use this template for systems that include the following service
processors:
v Remote Supervisor Adapter
v Remote Supervisor Adapter II

Chapter 10. Managing IBM BladeCenter and System x systems 537

 v Baseboard management controller (BMC)
This template is supported for scalable system partitions also.

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.

To specify the network IP for a System x service processor, complete the following
steps:
1. On the Configuration manager summary page, locate the Configuration tasks
section and click Create a template.
2. On the Templates page, click Create Template.
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 Service Processor
Network IP Configuration.
5. Type a name in the Configuration template name field.
6. Optional: Type a description in the Configuration template description field.
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 provided in the following steps.
12. 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.”
13. If you selected Get an IP address from the IP address pool, select an IP
address pool template.
14. If you selected Use the specified IP address, type the IP address, gateway,
and subnet mask.

Note: IPv4 addresses are accepted.

15. Click OK.
16. On the Service Processor Network IP Configuration page, select the node that
you created.
17. Click Save to save the changes in the configuration template. If you are
updating the configuration in real time, click Deploy.

538 IBMSystems Director Systems Management Guide

 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.
18. Optional: To return to the Templates page, click Cancel.
Related tasks
“Changing the integrated management module IP address by way of the Server
resource” on page 491
“Configuring the IP address pool for IBM BladeCenter systems and System x
servers” on page 532

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.

Note: You can use this template for systems that include the following service
processors:
v Remote Supervisor Adapter
v Remote Supervisor Adapter II
This template is supported for scalable system partitions also.

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.

To specify the SNMPv1 protocols for the service processor, complete the following
steps:
1. On the Configuration manager summary page, locate the Configuration tasks
section and click Create a template.
2. On the Templates page, click Create Template.
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 Service Processor
Network SNMP Configuration.
5. Type a name in the Configuration template name field.
6. Optional: Type a description in the Configuration template description field.
7. Click Continue. The Service Processor SNMP Configuration page is displayed.
8. 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.
9. In the Trap state list, select a status:
nothing-selected
Nothing is configured if this field is left blank.

Chapter 10. Managing IBM BladeCenter and System x systems 539

 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.
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.
14. 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.
15. Type a unique community name in the Community name field.
16. Type the value for the trap IP address or host name 1.

Note: IPv4 addresses are accepted.

17. Type the value for the trap IP address or host name 2.
18. Type the value for the trap IP address or host name 3.
19. Click OK to record the changes in the SNMP communities table.
20. In the table, select the community that you created.
21. 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 the page without making a selection and clicking
Save, no changes are made to the template and the information that you
entered is lost.
22. Optional: To return to the Templates page, click Cancel.

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
server. All settings might not be applicable for the supported components.

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:

540 IBMSystems Director Systems Management Guide

 1. On the Configuration manager summary page, locate the Configuration tasks
section and click Create a template.
2. On the Templates page, click Create Template.
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 Service Processor Ports
Configuration.
5. Type a name in the Configuration template name field.
6. Optional: Type a description in the Configuration template description field.
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.
11. 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.
12. Optional: To return to the Templates page, click Cancel.

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.

Note: You can use this template for systems that include the following service
processors:
v Remote Supervisor Adapter
v Remote Supervisor Adapter II
v Baseboard management controller (BMC)
This template is supported for scalable system partitions also.

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.

To configure an alert recipient, complete the following steps:

1. On the Configuration manager summary page, locate the Configuration tasks
section and click Create a template.
2. On the Templates page, click Create Template.
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 Service Processor Alert
Recipient.
5. Type a name in the Configuration template name field.
6. Optional: Type a description in the Configuration template description field.

Chapter 10. Managing IBM BladeCenter and System x systems 541

 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 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
Type the alert recipient’s IP address or host name.

Note: IPv4 addresses are accepted.

IBM Systems Director (comprehensive)
Type the alert recipient’s IP address or host name.

Note: IPv4 addresses are accepted.

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.

542 IBMSystems Director Systems Management Guide

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.

Important: If you close this page without clicking Save, no changes are made
to the template and the information that you entered is lost.
18. Optional: To return to the Templates page, click Cancel.

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:
1. On the Configuration manager summary page, locate the Configuration tasks
section and click Create a template.
2. On the Templates page, click Create Template.
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 Service Processor Alert
Recipient.
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 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.
17. 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 the page without making a selection and clicking
Save, no changes are made to the template and the information that you
entered is lost.
18. Optional: To return to the Templates page, click Cancel.

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.

Chapter 10. Managing IBM BladeCenter and System x systems 543

 Note: You can use this template for systems that include the following service
processors:
v Remote Supervisor Adapter
v Remote Supervisor Adapter II
This template is supported for scalable system partitions also.

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.

To specify alert settings, complete the following steps:

1. On the Configuration manager summary page, locate the Configuration tasks
section and click Create a template.
2. On the Templates page, click Create Template.
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 Service Processor Alert
Settings.
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 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.
14. 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.

544 IBMSystems Director Systems Management Guide

 15. Optional: To return to the Templates page, click Cancel.

Configuring IBM BladeCenter switch module protocols

Configuring the protocol for an IBM BladeCenter switch module consists of
configuring login, network protocols, SNMPv1 agents, and ports.

You can use this template for BladeCenter installations that include management
modules or advanced management modules. The settings provided by this
template 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. Both management modules and
advanced management modules provide applicable template settings for Ethernet
and FibreChannel switches. Only advanced management modules provide
applicable template settings for SAS switches.

To configure the IBM BladeCenter switch module protocols, complete the following
steps:
1. On the Configuration manager summary page, locate the Configuration tasks
section and click Create a template.
2. On the Templates page, click Create Template.
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 Switch Protocol
Configuration, where Switch is the switch model with the protocols that you
want to configure.
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 Switch Module Protocol Configuration page is displayed.
9. View the Login Configuration page and specify the user name, password, and
other information necessary for IBM Systems Director to log in to the switch
module:
a. Select the chassis slot number. All is the default selection.
b. Optional: Click Reset to factory-default settings to use the switch
factory-default user name and password to log into 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) Type the user name that is used to log into the switch. This user name
is validated by switch vendors. A default user ID of USERID can be
used.
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
IBM Systems Director Server.

Chapter 10. Managing IBM BladeCenter and System x systems 545

 10. Click the Network Protocols tab:
a. Select the static IP address configuration.
No IP address
The current switch IP address will be used.
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.

Note: IPv4 addresses are accepted.

e. In the HTTP list, select the type of access to grant to the switch module
when IBM Systems Director uses the Hypertext Transfer Protocol (HTTP)
protocol:
nothing selected
Specifies no selection.
Activate_read_only
Starts the switch module, using the HTTP protocol to read the
switch module only.
Activate
Starts the switch module and enables the HTTP protocol on the
switch.
Deactivate
Stops the switch module and disables the HTTP protocol on the
switch.
f. In the Telnet list, select the type of access to be granted to the switch
module when IBM Systems Director uses the Telnet protocol.
nothing selected
Specifies no selection.
Activate_read_only
Starts the switch module, using the Telnet protocol to read the
switch module only.
Activate
Starts the switch module and enables the Telnet protocol on the
switch.
Deactivate
Stops the switch module and disables the Telnet protocol on the
switch.
11. Click the SNMPv1 Agent tab.
a. Click Create. The Create New Community window is displayed.

546 IBMSystems Director Systems Management Guide

 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 module, but does not
permit changes to any of the configuration information.
Activate
Starts the SNMPv1 agent on the switch module and permits
changes to the configuration information.
Deactivate
Stops the SNMPv1 agent on the switch module.
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 are accepted.

f. Click OK.
12. Click the Port Configuration tab.
a. In the External ports list, select the type of access to grant to the switch
module when IBM Systems Director uses an external port:
nothing selected
Specifies that there is nothing configured
Activate_read_only
Starts the switch module but do not permit changes to any of the
configuration information on the switch module
Activate
Starts the switch module and permit changes to the configuration
information
Deactivate
Stops the switch module
13. If the switch module provides support for I/O protected mode, click the I/O
Protected Mode tab.
14. In the Protected mode field, set the protected mode state to either Deactivate
or Activate.
15. 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.”

Chapter 10. Managing IBM BladeCenter and System x systems 547

 e. If you selected Use the specified IP address, type the IP address, gateway,
and subnet mask.

Note: IPv4 addresses are accepted.

f. In the External ports table, select at least one port.
16. Configure the switch I/O-protected-mode properties. The following settings
are available:
Activate_read_only
Starts the switch module, but does not permit changes to any of the
configuration information on the switch module
Activate
Starts the switch module and permits changes to the configuration
information
Deactivate
Stops the switch module
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.
17. 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 the page without making a selection and clicking
Save, no changes are made to the template and the information that you
entered is lost.
18. Optional: To return to the Templates page, click Cancel.
Related tasks
“Configuring the IP address pool for IBM BladeCenter systems and System x
servers” on page 532

Configuring the IBM BladeCenter switch module virtual LAN

Configuring the virtual LAN (VLAN) for an IBM BladeCenter switch module
consists of running the VLAN configuration wizard.

You can use this template for BladeCenter installations that include management
modules or advanced management modules. The settings provided by this
template 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. Both the management modules and
advanced management modules provide settings for Ethernet switches in this
template.

To configure the IBM BladeCenter switch module VLAN, complete the following
steps:
1. On the Configuration manager summary page, locate the Configuration tasks
section and click Create a template.
2. On the Templates page, click Create Template.
3. In the Create Template window, select an appropriate target chassis from the
Template type list.

548 IBMSystems Director Systems Management Guide

 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.
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 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 VLAN communication with
the switch module. The default value is All, which indicates that the profile
applies to all chassis bays that include a VLAN switch module of this type. If
you select a specific bay number, the profile will apply only to VLAN switch
modules of the given type that are installed in the specified bay.
11. Click Next.
12. On the VLAN configuration page, click Create to create a new VLAN
configuration. 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. Type the interface number that is assigned to the VLAN ID.
17. Select a VLAN type.

Note: Only the settings supported by the switch module 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.
18. Select the VLAN status of Activate or Deactivate.
19. Click OK to return to the VLAN configuration page. The new VLAN
configuration is displayed in the table.
20. Click Next.
21. On the VLAN egress configuration page, click Create to create a new VLAN
egress configuration.
22. In the Create VLAN egress configuration window, select the VLAN ID
associated with the configuration on the previous page.
23. Select the port number. Valid values are from 1 - 20.
24. Select VLAN egress status.
No egress
Frames are not forwarded out of the port.

Chapter 10. Managing IBM BladeCenter and System x systems 549

 Tagged
Only tagged frames are forwarded out of the port.
Untagged
Only untagged frames are forwarded out of the port.
25. Click OK to return to the VLAN egress configuration table. The new VLAN
egress configuration is displayed in the table.
26. Click Next.
27. On the VLAN port configuration page, click Create to create a new VLAN
port.
28. In the Create VLAN port configuration window, select the port number. Valid
values are 1 - 20.
29. Type the port VLAN ID.
30. 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.
31. Select whether to activate the GARP VLAN Registration Protocol (GVRP)
status. GVRP dynamically adds VLANs to port egress lists across a domain.
32. 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.
33. Click OK to return to the VLAN port configuration table. The new VLAN
port configuration is displayed in the table.
34. Click Next.
35. On the Summary page, review your selections.
36. Optional: If you want to change any selections, click Back or select the page
from the wizard navigation area.
37. When you are satisfied with your selections, click Finish.

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:
1. On the Configuration manager summary page, locate the Configuration tasks
section and click Create a template.
2. On the Templates page, click Create Template.
3. In the Create Template window, select an appropriate target chassis from the
Template type list.

550 IBMSystems Director Systems Management Guide

 4. In the Configuration to create a template list, select User Authentication
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 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.
13. Optional: To return to the Templates page, click Cancel.

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:
v This template provides the function that was previously provided in earlier
versions of IBM Director by the Network Configuration task.
v The settings in this template are applied to the system by way of the Common
Agent or Platform Agent.

Configuring network adapters

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:

1. On the Configuration manager summary page, locate the Configuration tasks
section and click Create a template.
2. On the Templates page, click Create Template.
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 Network Configuration.
5. Type a name in the Configuration template name field.
6. Optional: Type a description in the Configuration template description field.
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.

Chapter 10. Managing IBM BladeCenter and System x systems 551

 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
“Configuring the IP address pool for IBM BladeCenter systems and System x
servers” on page 532
“Setting the search order for the DNS suffix”
“Configuring the domain or workgroup settings” on page 553

Setting the search order for the DNS suffix

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:

552 IBMSystems Director Systems Management Guide

 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
“Configuring network adapters” on page 551
“Configuring the domain or workgroup settings”

Configuring the domain or workgroup settings

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
“Configuring network adapters” on page 551
“Setting the search order for the DNS suffix” on page 552

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
BladeCenter blade servers.

Notes:
v This template provides the function that was previously provided in earlier
versions of IBM Director by the System Accounts task.
v The settings in this template are applied to the system by way of the Common
Agent or Platform Agent.

Chapter 10. Managing IBM BladeCenter and System x systems 553

 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
BladeCenter blade servers.

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:

1. On the Configuration manager summary page, locate the Configuration tasks
section and click Create a template.
2. On the Templates page, click Create Template.
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 System Account
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 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 running the Windows, Linux, or IBM i operating
system. Click Next.
12. On the General page, provide the following information about the user:
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) Select whether the user must change the user account
password when the user next logs in.
e. (Windows only) If you did not specify that the user must change the user
account password when the user next logs in, specify whether the user can
change the password.
f. (Windows only) Specify whether the user account password can expire.
g. (IBM i and Windows only) Specify whether the user account is active.
h. (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.

554 IBMSystems Director Systems Management Guide

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. In the Path field, type the configuration
file path.
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. Type the number of days after which the password will expire.
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
make changes, 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”

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
BladeCenter blade servers.

Chapter 10. Managing IBM BladeCenter and System x systems 555

 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:

1. On the Configuration manager summary page, locate the Configuration tasks
section and click Create a template.
2. On the Templates page, click Create Template.
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 System Account
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 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 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 make
changes, 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” on page 554

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.

Note: This template provides the function that was previously provided in earlier
versions of IBM Director by the Asset ID™ task.

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.

556 IBMSystems Director Systems Management Guide

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
Agent or Platform Agent.

To set asset information, complete the following steps:

1. On the Configuration manager summary page, locate the Configuration tasks
section and click Create a template.
2. On the Templates page, click Create Template.
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 Asset ID.
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 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

Chapter 10. Managing IBM BladeCenter and System x systems 557

 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.
16. Click Save to save the changes in the configuration template. If you are
updating the configuration in real time, click Deploy.

558 IBMSystems Director Systems Management Guide

 Important: If you close this page without clicking Save, no changes are made
to the template and the information that you entered is lost.
17. Optional: To return to the Templates page, click Cancel.

Chapter 10. Managing IBM BladeCenter and System x systems 559

560 IBMSystems Director Systems Management Guide
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
(HMC) 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.

For additional information about managing the virtualization and consolidation on

Power systems using IBM Systems Director, see the Managing IBM Power Servers
with IBM Systems Director 6.1 white paper on the Web at: www.ibm.com/
common/ssi/fcgi-bin/ssialias?infotype=SA&subtype=WH
&appname=STGE_PO_PO_USEN&htmlfid=POW03011USEN
&attachment=POW03011USEN.PDF
Related reference
Introduction to Virtualization

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.

© Copyright IBM Corp. 1999, 2009 561

 Power Systems term or
IBM Systems Director term concept
host server, system, managed
system
virtual server logical partition, partition
utility virtual server Virtual I/O Server (VIOS)
platform manager Hardware Management
Console (HMC) and
Integrated Virtualization
Manager (IVM)
power on activate (partition)
power off shut down (partition)
live relocation partition mobility, Live
Partition Mobility
static relocation inactive partition mobility,
inactive mobility
virtual farm N/A
562 IBMSystems Director Systems Management Guide
Definition
A physical server that
contains physical processors,
memory, and I/O resources
and which is often
virtualized into virtual
servers, also known as
logical partitions.
The collection of processor,
memory and I/O resources
defined to run an operating
system and its applications.
A virtual server that provide
virtualization capabilities for
a particular environment.
A platform manager
manages one or more hosts
and their associated virtual
servers and operating
systems. For Power Systems,
the platform managers are
HMC and IVM.
Power Systems managed by
HMC and IVM, use the term
power on with respect to a
physical server or host. IBM
Systems Director uses the
same term, power on, for
virtual servers, where Power
Systems has used the term
activate.
Power Systems managed by
HMC and IVM, use the term
power off with respect to a
physical server or host. IBM
Systems Director uses the
same term, power off, for
virtual servers, where Power
Systems has used the term
shut down.
Moving a running virtual
server from one host to
another
Moving a virtual server that
is powered off from one host
to another.
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:

1. In the IBM Systems Director navigation area, click Navigate Resources.
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 reference
AIX information in the IBM Systems Information Center

Managing Power Systems running IBM i

IBM Systems Director provides a fully integrated set of IBM i (formerly i5/OS)
management tasks as part of the Power Systems Management functionality.

IBM Systems Director 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

Chapter 11. Managing IBM Power Systems 563

 Note: To access these tasks, you must have requested access to the IBM i system,
and configured credentials. 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:

1. In the IBM Systems Director navigation area, click Navigate Resources.
2. Navigate to a managed system running IBM i. Make sure it is at Version 5
Release 4 or later.
3. Select the managed system running IBM i, click Actions from the menu bar,
and select i5/OS Management → task category where task category is the
category that includes the task you want to perform.
Related reference
i5/OS information

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 a variety of 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.
1. In the IBM Systems Director navigation area, click Navigate Resources.

564 IBMSystems Director Systems Management Guide

 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 will open in a new window, where you can perform
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 will open in a new window, where you can perform
the task.

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:
1. In the IBM Systems Director navigation area, click Welcome.
2. On the Welcome page, click Manage, 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
following information:
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

Chapter 11. Managing IBM Power Systems 565

 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 Links to the following tasks that you can use to get started with Power
Systems Management:
– System discovery
– Monitors
– Thresholds
– Check for updates
– Create virtual server
– BladeCenter management
– System Planning Tool

Monitoring for IBM i message queue events

To monitor for IBM i message queue events, create a customized event filter for
use in your event automation plans.

Note: This task requires the IBM Systems Director Launched Tasks program. This
program is installed automatically the first time you use a task that requires it. For
information about the IBM Systems Director Launched Tasks program, see
“Starting the IBM Systems Director Launched Tasks program.”

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.
3. In the Event Automation Plan wizard, the Welcome page is displayed. 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 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.

566 IBMSystems Director Systems Management Guide

 8. In the Create Filter window, select the simple filter type and click OK. The
IBM Systems Director Web interface starts the IBM Systems Director Launched
Tasks program. This program subsequently displays the Event Filter Builder
window.
9. In the Event Filter Builder window, clear the Any check box on the Event
Type page.
10. To specify IBM i message queue events, click Include IBM i message queue
events.
11. In the IBM i.Message Queue field, type the message queue event for which
you want to monitor and click Add. The event is displayed in the list box
below. If you want to remove an event, select it and click Delete.

Note: An IBM i message queue event has the following format:

OS/400.msgq.library/message_queue.messageID

where
v library is the library for the event monitor
v message_queue is the message queue for the event monitor
v messageID is the ID of the event monitor
The IBM i.Message Queue field automatically provides the common message
queue event prefix OS/400.msgq. You must type only the unique portion of the
message queue event, for example, QSYS/QSYSOPR.CPF0907.
Consider the following examples for monitoring message queue events. In
these examples, the library is QSYS and the message queue is QSYSOPR.
All message IDs that belong to a specific message library and message
queue Type QSYS/QSYSOPR in the IBM i.Message Queue field and click Add.
A specific message ID that belongs to a specific message library and queue
For example, if the message ID is CPF1234, type QSYS/
QSYSOPR.CPF1234 in the IBM i.Message Queue field and click Add.
A range of message IDs matching a specific pattern that belong to specific
message library and message queue
For example, to monitor for all message IDs that start with “CPF12”
(all messages from CPF1200 to CPF12FF), type QSYS/QSYSOPR in the
IBM i.Message Queue field and click Add. Then, click the Event Text
tab. On the Event Text page, clear the Any check box and type the
message ID pattern, for example CPF12, in the Event Text field. Also,
make sure Any word is selected.
12. Click File → Save As.
13. In the Save Event Filter window, type a name for the filter.
14. Click OK to save the filter. The new filter is displayed on the Events page.
15. Click Next.
16. On the Event actions page, click Create.
17. In the Create Actions window, select an event action, for example, Send an
e-mail (Internet SMTP)
18. Click OK.
19. 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.”
20. When you are satisfied with the settings, click OK.

Chapter 11. Managing IBM Power Systems 567

 21. When you are satisfied with your selected event actions, click Next.
22. On the Time range page, choose the period of time over which you want to
collect the events. Select All day (24 x 7) to enable the plan to be active all the
time.
23. When you are satisfied with the specified time ranges, click Next.
24. On the Summary page, verify the details of the event automation plan. If you
need to make changes, click < Back.
25. 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.

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.

Power On/Off task support by way of the operating system on

IBM Power systems
Support for the Power On/Off task is provided by the operating system on IBM
Power systems. Whether you have Platform Agent or Common Agent installed on
the system can also affect the support.

See the following table for more information.

Table 36. Power-state-setting support by operating systems on IBM Power systems
Power settings
Operating system supported
1
v AIX Version 5.2 Yes
v IBM AIX Version 5.3 Yes2
v IBM AIX Version 6.1
v Red Hat Enterprise Linux AS, versions 4.6 and 4.7, on IBM
Power Systems
v Red Hat Enterprise Linux Advanced Platform, versions 5.1
and 5.2, on IBM Power Systems
v SUSE Linux Enterprise Server 9 on IBM Power Systems
(supports Service Packs 3 and 4)
v SUSE Linux Enterprise Server 10 on IBM Power Systems
(supports Service Packs 1 and 2)

1. Power On/Off and Restart is supported on IBM Director Agent version 5.20 and
Agentless systems.
2. Power On/Off and Restart support provided for Agentless-, Platform Agent-, or
Common Agent-managed systems.

Note: Power On/Off and Restart support is also provided for Integrated
Virtualization Manager and Virtual I/O Server.

Changing the power state on IBM Power systems

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 IBM Power systems.”

568 IBMSystems Director Systems Management Guide

You must have access to the system to change the power state. For information
about requesting access to a system, see “Requesting access to a secured system.”

To change the power state, complete the following steps:

1. In the IBM Systems Director Web interface navigation area, click Navigate
Resources.
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 you
want to invoke. 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 Run window, click OK to change the power state immediately. You also
can schedule this task to run at a later time. For more information, see
“Scheduling tasks.”

Chapter 11. Managing IBM Power Systems 569

570 IBMSystems Director Systems Management Guide
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.

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
PDF files″ at the z/VM library.

The z/VM control program

A core component of the z/VM operating system is the control program (CP). 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.

© Copyright IBM Corp. 1999, 2009 571

 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 26. z/VM virtual servers

The z/VM user directory

z/VM 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 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.

572 IBMSystems Director Systems Management Guide

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.

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 27. 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.

Figure 28. z/VM virtual servers connected to a guest LAN

Chapter 12. Managing IBM System z systems 573

 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 29. 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 30. z/VM virtual servers connected to a HiperSockets network

With HiperSockets you can span multiple LPARs on the same mainframe.
Related reference
z/VM PDF files

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
574 IBMSystems Director Systems Management Guide
 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.

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:

1. In the IBM Systems Director navigation area, click Welcome.
2. On the Welcome page, click Manage, 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 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
Chapter 12. Managing IBM System z systems 575
 – 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
If the Hardware Management Console is running Simple Network
Management Protocol (SNMP) version 1 (v1) and a public profile, you can
use the System Discovery task to 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 use the Advanced System
Discovery task to discover the physical systems managed by the HMC.

576 IBMSystems Director Systems Management Guide

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 following operating systems:
v Red Hat Enterprise Linux AS, version 4.0, for IBM System z
v Red Hat Enterprise Linux AS, version 5.0, for IBM System z
v SUSE Linux Enterprise Server 9 for IBM System z
v SUSE Linux Enterprise Server 10 for IBM System z

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.”

You must have access to the system to change the power state. For information
about requesting access to a system, see “Requesting access to a secured system.”

To change the power state, complete the following steps:

1. In the IBM Systems Director Web interface navigation area, click Navigate
Resources.
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 you
want to invoke. 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 Run window, click OK to change the power state immediately. You also
can schedule this task to run at a later time. For more information, see
“Scheduling tasks.”

Chapter 12. Managing IBM System z systems 577

578 IBMSystems Director Systems Management Guide
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.

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.

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.

© Copyright IBM Corp. 1999, 2009 579

 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
using a standard interface based on the Common Information Model (CIM)

protocol.

IBM Systems Director recognizes certain storage devices that comply with the
Storage Management Initiative Specification (SMI-S). This is an industry standard
developed by the Storage Networking Industry Association (SNIA). IBM Systems
Director supports SMI-S versions 1.1.

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. IBM Systems Director obtains information about
storage devices through the SMI-S provider’s Common Information Model Object
Manager (CIMOM) component. Communication occurs 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
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 alternate port number. When you add a storage
device whose provider is using an alternate port number to your 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 will be 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 in order 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.

580 IBMSystems Director Systems Management Guide

Storage devices that require an SMI-S provider
These storage devices require an SMI-S provider in order to work with IBM
Systems Director.
v IBM System Storage DS3200 devices
v IBM System Storage DS3300 devices
v IBM System Storage DS3400 devices
v IBM TotalStorage DS4000 devices
v IBM TotalStorage DS6000 devices
v Brocade 2G/4G Fibre Channel (IBM BladeCenter chassis and external)
v Brocade Blade Server SAN I/O Modules
v Brocade 4 Gbit/sec SAN I/O Modules

For the Qlogic 2 Gbit/sec and 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 6.1.0
Linux
v PlatformAgentSubagent IBM BladeCenter SAS RAID Controller Module 6.1.0
Windows

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.

Applicable standards

For information about the standards mentioned here, see these Web sites:
SMI-S https://www.snia.org/smi/about/
SNIA https://www.snia.org
DMTF
www.dmtf.org
WBEM
www.dmtf.org/standards/wbem/
CIM www.dmtf.org/standards/cim

Chapter 13. Managing and configuring storage 581

 Where to obtain SMI-S providers
Use the following information to obtain SMI-S providers for any IBM TotalStorage
DS3000, DS4000, or DS6000 devices, or various switches used to manage storage
devices.
IBM TotalStorage DS4000 or DS3000
The SANtricity SMI Provider from LSI that complies with SMI-S version
1.1 is required to enable discovery of IBM System Storage DS4000 or
DS3000 devices. You can obtain this provider from the LSI Web site at
www.lsi.com/storage_home/products_home/external_raid/
management_software/smis_provider/.

Note: If you want to manually add a IBM System Storage DS4000 or

DS3000 device using IBM Systems Director, you must specify the IP
address of the system where you installed the SANtricity SMI Provider, not
the IP address of the IBM System Storage DS4000 or DS3000 device itself.
IBM TotalStorage DS6000
You can obtain the provider for the IBM TotalStorage DS6000 from this
Web site: www-304.ibm.com/systems/support/supportsite.wss/
supportresources?taskind=2&brandind=5000033&familyind=5329497.
Brocade switches
You can obtain the appropriate SMI-S version 1.1 provider for IBM Systems
Director from this Web site: www.brocade.com/support/SMIAGENT.jsp.
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.

Installing SMI-S Providers

IBM Systems Director requires SMI-S 1.1 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.

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.
a. The SMI-S provider for IBM TotalStorage DS3000 and DS4000 storage
systems can be found at this Web site: www.lsi.com/storage_home/
products_home/external_raid/management_software/smis_provider/.
b. The SMI-S provider for IBM TotalStorage DS6000 storage systems can be
found at this Web site: www.ibm.com/systems/support/supportsite.wss/
supportresources?taskind=2&brandind=5000033&familyind=5329497.
c. The SMI-S provider for the Brocade switch can be found at this Web site:
www.brocade.com/support/SMIAGENT.jsp.
2. Register the SMI-S provider with IBM Systems Director. Use basic Discovery for
this by specifying the IP Address or hostname of the system. This uses SLP to
locate the provider and query the relevant attributes.
3. Unlock the SMI-S provider, which requires a user ID and password.

582 IBMSystems Director Systems Management Guide

4. Once 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.

Installing the SMI-S provider for the IBM BladeCenter S SAS

RAID Controller Module on additional systems
the SMI-S provider for the IBM 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 Platform-Agent managed
systems, and have these systems also perform storage management tasks.

The SMI-S provider for the IBM BladeCenter S SAS RAID Controller Module has
one of these operating-system dependent names:
v PlatformAgentSubagent IBM BladeCenter SAS RAID Controller Module 6.1.0
Linux
v PlatformAgentSubagent IBM BladeCenter SAS RAID Controller Module 6.1.0
Windows

Before installing the PlatformAgentSubagent IBM BladeCenter SAS RAID

Controller Module 6.1.0 Linux or PlatformAgentSubagent IBM BladeCenter SAS
RAID Controller Module 6.1.0 Windows, ensure that you have already installed
Platform Agent on the managed system. It is possible to install the subagent
without this prerequisite, but the installation will complete with errors and you
will not be able to use the subagent.

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 the IBM BladeCenter S SAS RAID Controller
Module on another system, complete the following steps:
1. Select the target system in the Navigate Resources area. Note: Inventory
collection should be run on the target system before this step.
2. Click Actions → Release Management → Install Agent. The Install Agent wizard
is displayed.
3. In the Install Agent Wizard, choose the name of the SMI-S provider:
v PlatformAgentSubagent IBM BladeCenter SAS RAID Controller Module
6.1.0 Linux
v PlatformAgentSubagent IBM BladeCenter SAS RAID Controller Module
6.1.0 Windows
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 will manage some of the storage
systems formerly managed by the source provider.
8. If necessary, repeat these steps for additional target systems, until the source
system has a more reasonable workload.

Chapter 13. Managing and configuring storage 583

 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 LSI ESG SMI-S provider on Windows systems

The LSI ESG SMI-S provider is needed to manage IBM TotalStorage DS3000 and
DS4000 storage systems. Use these instructions to install the LSI ESG SMI-S
provider on Windows systems.

First, obtain this SMI-S provider from the supplier. See this Web site:
www.lsi.com/storage_home/products_home/external_raid/
management_software/smis_provider/index.html?remote=1&locale=EN.

To install the LSI ESG SMI-S provider on Windows systems, complete the
following steps:
1. Run the installation exec, such as Windows_Installer-WS32-10.35.30.00.exe.
The InstallAnywhere welcome page is displayed.
2. Click Next. The InstallAnywhere License Agreement page is displayed.
3. Read the License Agreement carefully.
4. Click I accept the terms of the License agreement.
5. Click Next. The Where would you like to Install? page is displayed.
6. Type the location where you would like the SMI-S provider to be installed, or
use the default folder name provided.
7. Click Next. The Summary page is displayed.
8. Ensure that everything on this page is correct.
9. Optional: If some of the values on this page are not correct, click Previous and
return to the page where this data was entered and make corrections.
10. Click Install. The Create/Edit ArrayHosts.txt file page is displayed.
11. Enter the IP addresses of controllers in the IBM TotalStorage DS3000 and
DS4000 storage system.
a. If there are two controllers in the IBM TotalStorage DS3000 and DS4000
storage system, enter the IP address of both of them.
b. If there is only one controller, enter its IP address.
12. Click OK. When the installation process is complete, a page is displayed
saying that the LSI ESG SMI-S provider has been successfully installed.
13. Clock Done. The InstallAnywhere wizard terminates.

Now that the installation is finished, you must enable authentication.

Installing the LSI ESG SMI-S provider on AIX and Linux systems
The LSI ESG SMI-S provider is needed to manage IBM TotalStorage DS3000 and
DS4000 storage systems. Use these instructions to install the LSI ESG SMI-S
provider on AIX and Linux systems.

First, obtain this SMI-S provider from the supplier. See this Web site:
www.lsi.com/storage_home/products_home/external_raid/
management_software/smis_provider/index.html?remote=1&locale=EN.

To install the LSI ESG SMI-S provider on AIX and Linux systems, consult this Web
site www.lsi.com/storage_home/products_home/external_raid/
management_software/smis_provider/index.html?remote=1&locale=EN, and view
the Readme file for your operating system. Follow the instructions in this file.

584 IBMSystems Director Systems Management Guide

Now that the installation is finished, you must enable authentication.

Installing the IBM TotalStorage DS6000 SMI-S provider

Use these instructions to install and configure the SMI-S provider for IBM
TotalStorage DS6000 storage devices.

First, obtain this SMI-S provider from the supplier and unzip the files to a local
directory.

To install the SMI-S provider for the IBM TotalStorage DS6000 system, complete
the following steps:
1. Run Setup.exe from the W2003 directory. The Welcome page is displayed.
2. Read the Welcome page and then click Next. The Software License Agreement
page is displayed.
3. Read this page carefully.
4. Click I accept the terms in the license agreement.
5. Click Next. The Destination Directory page is displayed.
6. Click Next. The Server Communication Configuration page is displayed.
7. Click Next. The Configuration Parameters page is displayed.
8. Type the user ID and password that you want used to communicate with the
SMI-S provider.
9. Click Add. The Add New Device popup is displayed.
10. Type the following information about the Storage Manager Console:
a. Device Type - DS
b. IP Address - the IP address of the Storage Manager Console of the IBM
TotalStorage DS6000 storage system.
c. Optional: Alternate IP - An alternate IP address for the Storage Manager
Console.
d. User Name - The user ID to log in the Storage Manager Console.
e. Password - The password to log in the Storage Manager Console.
11. Click OK. The information just entered is displayed in the table on the
Configuration Parameters page.
12. Optional: Click Add to create another entry.
13. Optional: Highlight an entry and click Modify to change an existing entry.
14. Optional: Click Remove to delete an entry.
15. When this table is correct, click Next. The Install Preview page is displayed.
16. Verify the information on this page.
17. Optional: If anything is incorrect, click Back to return to previous pages and
make corrections.
18. Click Install. The installation process runs. When finished, the Installer -
Finish page is displayed.
19. Click Finish. This application terminates.
Related tasks
“Verifying the SMI-S provider for the IBM TotalStorage DS6000 storage system” on
page 589

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.

Chapter 13. Managing and configuring storage 585

 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. The License Agreement page is displayed.
2. Read the License Agreement.
3. Click I accept the terms of the License Agreement.
4. Click Next. The System Configuration page is displayed.
5. Click Next. The Introduction page is displayed.
6. Click Next. The Choose Installation Folder page is displayed.
7. Click Next. The HTTP Port Configuration page is displayed.
8. Click Next. The HTTPS Port Configuration page is displayed.
9. Click Install. The FabricManager Server Configuration page is displayed.
10. Click Next. The Enabling Mutual Authentication for Client page is displayed.
11. Click Next. The Enabling Mutual Authentication for Indications page is
displayed.
12. Click Next. The Enabling Security page is displayed.
13. Click Next. The Eventing and ARR TCP Port Configuration page is displayed.
14. Click Next. The Enabling Console And/Or File Logging page is displayed.
15. Click Next. The Proxy Connections Configuration page is displayed.
16. Click Add. The Proxy Configuration popup is displayed.
17. Enter these values:
a. Proxy IP - The IP address of the Brocade switch.
b. User name - The user ID used to access the Brocade switch.
c. Password - The password used to access the Brocade switch.
d. Login-scheme - Standard.
e. No. of RPC Handles - 5.
18. Click OK. The information that you just entered is displayed in the table on
the Proxy Connections Configuration page.
19. Optional: Click Add to create another entry.
20. Optional: Highlight an entry and click Modify to change an existing entry.
21. Optional: Click Remove to delete an entry.
22. When this table is correct, click Next. The Important Information page is
displayed.
23. Verify the information on this page.
24. Optional: If anything is incorrect, click Previous to return to previous pages
and make corrections.
25. Click Next. The Configuring and Starting as a Service page is displayed.
26. For the question: Do you want to start SMI Agent as a Service, click Yes.
27. Click Next. The installation process runs. When finished, the Installation
Completed page is displayed.
28. Click Done. This application terminates.

When finished, proceed to the next topic to install and configure the SLP service.

586 IBMSystems Director Systems Management Guide

 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.

Configuring 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.

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. This SMI-S provider has one of these names:
PlatformAgentSubagent IBM BladeCenter SAS RAID Controller Module 6.1.0 Linux
or PlatformAgentSubagent IBM BladeCenter SAS RAID Controller Module 6.1.0
Windows.

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 Navigate Resources → 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. This SMI-S provider has one of these names:

Chapter 13. Managing and configuring storage 587

 PlatformAgentSubagent IBM BladeCenter SAS RAID Controller Module 6.1.0
Linux or PlatformAgentSubagent IBM BladeCenter SAS RAID Controller
Module 6.1.0 Windows.
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.
8. Type the User ID and Password for the management port. The default User ID
and Password are USERID1 and PASSW0RD (with a zero). These should be
used unless they have been changed.
9. Click OK to save the changes.
Related tasks
“Managing IBM BladeCenter and System x storage devices” on page 606

Enabling Authentication for the LSI ESG SMI-S provider

Once 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.

To enable authentication for the LSI ESG SMI-S provider, complete the following
steps:
1. Stop the SMI-S provider service by clicking Service → Engenio SMI-S Provider
Server → Actions → Stop.
2. Edit the cimom.properties file located in the wbemservices/cimom/bin folder.
3. This file contains a list of available authentication providers. A ’#’ in front of
the name indicates that it is not selected (commented out).
4. Choose the authentication provide that you want by removing the ’#’ that is in
front of it.
v BasicUserPasswordProvider authentication indicates that domain and local
users can authenticate on Windows systems. If running with Virtual Private
Network, domain authentication does not function. Only local users can
authenticate on Unix systems.
v CredentialsBasedPasswordProvider indicates that initially all users can
authenticate.
To secure the system, create an instance of <OEM>_CIMOMSharedSecret in
the ’/interop’/ namespace. The following keys must be populated with the
following values:
– SystemCreatonClassName = ″<OEM>_StorageManagementSystem″
– CreationClassName = ″<OEM>_CIMOMSharedSecretService″
– ServiceName = ″CIMOMSharedSecretService″
– SystemName = ″CIMOM_IP
– RemoteId = USER_CHOICE

588 IBMSystems Director Systems Management Guide

 If you want a password, you must also populate the Secret property with a
password of your choice. With this authentication enabled, only user ID and
password combinations created as <OEM>_CIMOMSharedSecret instances
can access the CIMOM.
To remove a user, delete the appropriate instance.
v UnsecureUserPasswordProvider indicates that you request access to the
provider by specifying anything for the userid and password; authentication
is not checked.

Now that the authentication is enabled, you must verify this SMI-S provider.

Verifying the LSI ESG SMI-S provider:

Once you have enabled authentication, verify the installation and configuration of
this SMI-S provider.

To verify the LSI ESG 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 LSI ESG 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.

Verifying the SMI-S provider for the IBM TotalStorage DS6000 storage system:

Use this task to verify that the SMI-S provider for the IBM TotalStorage DS6000 has
been correctly configured.

To verify the SMI-S provider for the IBM TotalStorage DS6000 storage system,
complete the following steps:
1. Open a command window.
2. Issue this command: dscimcli lsuser.
The output is similar to this:

Chapter 13. Managing and configuring storage 589

 Username
========
admin
superuser

You should see the user IDs that you have defined.
3. Issue this command: dscimcli lsdev -l.
The output is similar to this:

TYPE IP IP2 Username Storage Image Status Code Level Min Codelevel
=========================================================
DS 22.33.44.55 - admin IBM.1750–1300019 successful 5.2.2.272 5.0.6.235
DS 22.33.44.66 - admin IBM.1750–1300000 successful 5.2.2.272 5.0.6.235

If you do not see information similar to this, first retry the installation of the SMI-S
provider. If that does not resolve the problem, contact your service provider.
Related tasks
“Installing the IBM TotalStorage DS6000 SMI-S provider” on page 585

Discovering and collecting inventory for storage devices

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
“Discovery manager” on page 10
“Manageable resource types” on page 7
“Manageable systems” on page 7
“Discovery” on page 231
“Discovery protocols” on page 232
“System discovery” on page 237
“Discovery profiles” on page 239
Related tasks
Chapter 3, “Discovering systems and collecting inventory data,” on page 231
“Performing a system discovery” on page 32
“Creating a discovery profile” on page 34
“Performing an advanced system discovery” on page 48

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 is a basic discovery procedure.

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 that have
the storage that the SMI-S Provider controls. To run System Discovery for systems
that have a SMI-S Provider, complete the following steps:
1. From the Navigation area of the Welcome page click Inventory → System
Discovery The System Discovery page is displayed.
2. Click Single system (IP address).

590 IBMSystems Director Systems Management Guide

 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.
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 just discovered.

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 is an advanced discovery procedure.

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 that have
the storage that the SMI-S Provider will access. The auto-unlock feature must be
used for this function to work properly.

To run Advanced System Discovery for systems that have a SMI-S Provider,
complete the following steps:
1. From the Navigation area of the Welcome page click Inventory → Advanced
System Discovery The Advanced System Discovery page is displayed.
2. Click Actions → Create. The Advanced Discovery wizard is invoked.
3. If you see the Welcome page:
a. Clear Show this Welcome page next time if you do not want to see the
Welcome page next time.
b. Click Next.
The Profile Properties page is displayed.
4. Type a name for the Discovery profile that you are creating.
5. Select a profile type of Operating System. SMI-S providers are viewed as if
they were operating systems.
6. Type a description of the new profile.
7. Click Next. The Protocol selection page is displayed.
8. Click Storage Management Initiative Specification (SMI-S) Discovery.
9. Click Next. The SMI-S Configuration page is displayed.
10. Select the type of discovery. Click Direct Connection.
11. Choose the Hardware type:
v IBM system storage DS3000/DS4000
v IBM system storage DS6000
v Brocade fibre channel switch
v IBM BladeCenter S SAS RAID Controller Module
12. Choose the protocol:

Chapter 13. Managing and configuring storage 591

 v https
v http
If you selected a Hardware type of IBM BladeCenter S SAS RAID Controller
Module, you cannot select a protocol. http protocol will always be used.
13. Type the IP address of the SMI-S Provider.
14. The Port number field will be filled in with the default port number for the
chosen protocol. To use a different port number, type it in the Port field. You
would use a different port number if the default one had already been used
for another SMI-S Provider.
15. If you selected a Hardware type of IBM system storage DS3000/DS4000, the
default port number is 5988.
16. If you selected a Hardware type of IBM BladeCenter S SAS RAID Controller
Module, the default port number displayed will be 5988. This might not be
correct, depending on the operating system that hosts this SMI-S provider.
Review these choices and correct the port number if necessary.
v 5988 is the default port number for the SMI-S provider of the IBM
BladeCenter S SAS RAID Controller Module when running on Microsoft
Windows 2003.
v 15988 is the default port number for the SMI-S provider of the IBM
BladeCenter S SAS RAID Controller Module when running on Linux.
17. Click Next. The Access Request page is displayed.
18. Click Activate. The activates the auto-unlock feature.
19. Type the user ID and password to access the system.
20. Click Next. The Inventory Discovery page is displayed.
21. Select whether to automatically run Inventory Discovery on newly-discovered
resources.
22. Click Next. The Summary page is displayed.
23. Examine the Advanced Discovery information on this page carefully.
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 Advanced System Discovery profiles is displayed, with an entry for
the new profile that you just created.
24. Select this profile and click Run. A scheduler pop-up is displayed below the
table of profiles.
25. Choose to run the task now, or specify options for running later.
26. Click OK.
27. Wait for the task to complete. Monitor the job status to see when it is finished.
28. When the task completes, go to the SMI-S Providers storage group by clicking
Navigate Resources → Groups → Groups by System Type → Storage Systems.
The storage will be displayed in the Network Storage group. The SMI-S
providers group will also have the systems with the SMI-S provider installed.
29. Select a system.
30. If the Access field indicates No Access:
a. Click the No Access link.
b. Type a User ID and Password for the system.
c. Click Request Access.
Access to the system is established.

592 IBMSystems Director Systems Management Guide

 31. From the Resource Navigator, a list of storage devices is displayed along with
the system that was just discovered.

Running Advanced Discovery for multiple SMI-S providers

using multicast and broadcast
Using multicast and broadcast, multiple SMI-S providers can be discovered at
once. This is an advanced discovery procedure.

Service Location Protocol (SLP) is the protocol used for SMI-S multicast and
broadcast discovery. SLP is used for clients to locate servers and other services on
the network. This procedure is using two advanced SLP methods, multicast and
broadcast, to find all SMI-S providers. It does the following:
v Send an SLP request to the default multicast group.
v Send an SLP request to the broadcast group.
v Using these two functions, try to find all your SMI-S providers.

To run advanced discovery for multiple SMI-S providers using multicast and
broadcast, complete the following steps:
1. From the Navigation area of the Welcome page click Inventory → Advanced
System Discovery The Advanced System Discovery page is displayed.
2. Click Actions → Create. The Advanced Discovery wizard is invoked.
3. If you see the Welcome page:
a. Clear Show this Welcome page next time if you do not want to see the
Welcome page next time.
b. Click Next.
The Profile Properties page is displayed.
4. Type a name for the Discovery profile that you are creating.
5. Select a profile type of Operating System. SMI-S providers are viewed as if
they were operating systems.
6. Type a description of the new profile.
7. Click Next. The Protocol selection page is displayed.
8. Click Storage Management Initiative Specification (SMI-S) Discovery.
9. Click Next. The SMI-S Configuration page is displayed.
10. Select the type of discovery. Click Multicast and broadcast.
11. Click Enable multicast.
12. Click Enable general broadcast.
13. Choose a timeout period of 60 seconds.
14. Click Next. The Access Request page is displayed.
15. Optional: Click Deactivate. Since multiple SMI-S providers are discovered, it
is not advisable to choose Activate. Unless all discovered SMI-S providers had
the exact same User ID and password, the access request would fail.
16. Click Next. The Inventory Discovery page is displayed.
17. Click Deactivate.
18. Click Next. The Summary page is displayed.
19. Examine the Advanced Discovery information on this page carefully.
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.

Chapter 13. Managing and configuring storage 593

 A table of Advanced System Discovery profiles is displayed, with an entry for
the new profile that you just created.
20. Select this profile and click Run. A scheduler pop-up is displayed below the
table of profiles.
21. Choose to run the task now, or specify options for running later.
22. Click OK.
23. Monitor the status of this job. It could potentially take a long time.
24. To see the systems with SMI-S Providers as they are discovered, click
Navigate Resources → Groups → All Systems. As the systems with SMI-S
providers are discovered, they will be added to this page.

Running Advanced Discovery for SMI-S providers using a

directory agent
Using a directory agent, multiple SMI-S providers can be discovered at once. This
is useful to find SMI-S providers that are on a different subnet that the
management server. This is an advanced discovery procedure.

Service Location Protocol (SLP) is the protocol used for SMI-S directory agent
discovery. SLP is used for clients to locate servers and other services on the
network. This procedure is using a directory agent to find all SMI-S providers. This
is useful if an SMI-S provider is located on a different subnet.

A scope is used to categorize SMI-S providers. A scope is a list of SMI-S providers

defined in the directory agent. If a scope is used in this procedure, a particular
SMI-S provider will not be discovered unless it is listed in the scope.

To run advanced discovery for multiple SMI-S providers using a directory agent,
complete the following steps:
1. From the Navigation area of the Welcome page click Inventory → Advanced
System Discovery The Advanced System Discovery page is displayed.
2. Click Actions → Create. The Advanced Discovery wizard is invoked.
3. If you see the Welcome page:
a. Clear Show this Welcome page next time if you do not want to see the
Welcome page next time.
b. Click Next.
The Profile Properties page is displayed.
4. Type a name for the Discovery profile that you are creating.
5. Select a profile type of Operating System. SMI-S providers are viewed as if
they were operating systems.
6. Type a description of the new profile.
7. Click Next. The Protocol selection page is displayed.
8. Click Storage Management Initiative Specification (SMI-S) Discovery.
9. Click Next. The SMI-S Configuration page is displayed.
10. Select the type of discovery. Click Proxy - using directory agents.
11. Click Add to move the IP address of the directory agent to the Specified IP
addresses list.
12. Optional: Repeat the previous two steps until all directory agents are added.
13. Optional: If any value in the Specified IP addresses list is incorrect, click
Delete to delete it.

594 IBMSystems Director Systems Management Guide

 14. Optional: Type values in the Scope field. These values are the names of the
scopes defined in the directory agent. The scope limits the discovery task to
only those providers listed in the scope area of the directory agent.
15. Click Next. The Access Request page is displayed.
16. Optional: Click Deactivate. Since multiple SMI-S providers are discovered, it
is not advisable to choose Activate. Unless all discovered SMI-S providers had
the exact same User ID and password, the access request would fail.
17. Click Next. The Inventory Discovery page is displayed.
18. Click Deactivate.
19. Click Next. The Summary page is displayed.
20. Examine the Advanced Discovery information on this page carefully.
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 Advanced System Discovery profiles is displayed, with an entry for
the new profile that you just created.
21. Select this profile and click Run. A scheduler pop-up 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
Navigate Resources → Groups → All Systems. As the systems with SMI-S
providers are discovered, they will be added to this page.

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. These
applications should already be installed, but if they are not, consult the appropriate
documentation to acquire and install them.

The external storage management application to be run must be installed or

accessible. You must have run inventory collection on the storage devices in order
to launch an external storage management application for those storage devices.

This list describes the application to be used for each storage device.
v IBM TotalStorage Productivity Center for SAN-attached devices
v DS4000 Storage Manager for IBM DS3200, DS3300, DS3400, and DS4000 storage
devices
v IBM DS Storage Manager for DS6000 storage devices
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 The IBM TotalStorage Productivity
Center can be launched after having selected a target resource.

Chapter 13. Managing and configuring storage 595

 Installing and configuring external storage applications
Storage systems management uses some storage applications, which must be
installed and configured prior to managing storage devices.

Installing and configuring IBM TotalStorage Productivity Center

If you want to use IBM TotalStorage Productivity Center in conjunction with IBM
Systems Director, IBM TotalStorage Productivity Center must be installed and
properly configured. You can either use an existing installation of IBM TotalStorage
Productivity Center or you can download IBM TotalStorage Productivity Center
Limited Edition.

To install and configure IBM TotalStorage Productivity Center, complete the

following steps:
1. Download IBM TotalStorage Productivity Center Limited Edition from the
Passport Advantage® Web page.
2. For instructions on how to install IBM TotalStorage Productivity Center, see the
IBM TotalStorage Productivity Center Installation and Configuration Guide.

Notes:
v The directory to which you extract the IBM TotalStorage Productivity Center
code for installation and the directory where you choose to install IBM
TotalStorage Productivity Center both have a limit of 60 characters in the
path name.
v The source directory from which IBM TotalStorage Productivity Center is
installed cannot have a hyphen character (-) anywhere in the path name.
v For additional installation and configuration tips, see the Support for IBM
TotalStorage Productivity Center for Data Web page. Under the V3.1 heading,
click Technical notes. Then search for Hints and Tips.
3. If IBM TotalStorage 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 TotalStorage Productivity Center.

Configuring SNMP trap forwarding for IBM TotalStorage

Productivity Center
If IBM TotalStorage Productivity Center is installed on the same system as IBM
Systems Director, you must configure SNMP trap forwarding between IBM
Systems Director and IBM TotalStorage Productivity Center.

You do not need to configure SNMP trap forwarding if IBM Systems Director and
IBM TotalStorage 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 TotalStorage Productivity Center are installed.
c. Remove the # character at the beginning of this line:
#snmp.trap.v1.forward.port.1=

596 IBMSystems Director Systems Management Guide

 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 TotalStorage 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
TotalStorage 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 TotalStorage Productivity Center server.

Installing and configuring IBM DS Storage Manager for DS4000

To use the IBM TotalStorage DS4000 devices, you must obtain the IBM DS Storage
Manager for DS4000. This application can also be used for IBM DS3200, DS3300,
and DS3400 devices.

To install and configure the IBM DS Storage Manager for DS4000, complete the
following steps:
1. Go to this Web site and download the IBM DS Storage Manager for DS4000.
www.lsi.com/storage_home/products_home/external_raid/
management_software/smis_provider/index.html?remote=1&locale=EN
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.

Installing and configuring IBM DS Storage Manager for DS6000

In order to use the IBM TotalStorage DS6000 devices, you must obtain the IBM DS
Storage Manager for DS6000.

To install and configure the IBM DS Storage Manager for DS6000, complete the
following steps:
1. Go to this Web site and download the IBM DS Storage Manager for DS6000.
www.ibm.com/systems/support/supportsite.wss/supportresources?taskind=2
&brandind=5000033&familyind=5329497
2. Configure the IBM DS Storage Manager for DS6000 according to the
instructions found on the Web site, and any Readme or similar files that you
find.

Chapter 13. Managing and configuring storage 597

 Installing and configuring ServeRAID Manager
For some ServeRAID controllers, you must install ServeRAID Manager V9.00.
Follow these instructions to install and configure this software. IBM Systems
Director 6.1 supports only V9.00 of ServeRAID Manager.

You must have an IBM ServeRAID Application CD V9.00 - Servers and

IntelliStation®. You might have received one with certain IBM products. If not, you
can download IBM ServeRAID Application CD V9.00 - Servers and IntelliStation
from the Software Matrix Web site at www.ibm.com/systems/support/
supportsite.wss/docdisplay?brandind=5000008&lndocid=SERV-RAID. This CD is
used to install all necessary ServeRAID software.

When viewing the contents of this CD, these 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.1.

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
v LSI-1030 integrated RAID controller
2. Install IBM Systems Director 6.1 Common Agent on the system that hosts the
RAID adapter, if you have not already done this.
3. After the Common Agent is installed, go to the folder that contains ServeRAID
Manager extension packages and run the ServeRAID Manager Level-1 Agent
setup.
4. Navigate to the folder of ServeRAID Manager 9.00 Application CD, and install
ServeRAID Manager Agent. (Standalone Edition). Now on the system that hosts
the RAID adapter, the following features have been installed:
a. Director Agent (shown as ’IBM Director Agent’) and ’IBM Director Core
Services’, which is the Platform Agent.
b. ’ServeRAID Manager for Director Core Services’, which is the ServeRAID
Manager Level 1 Agent.
c. ’ServeRAID Manger’, the ServeRAID Manager Agent (Standalone Edition).
5. On the system running the Web browser (IBM Systems Director Web interface),
navigate to the folder of ServeRAID Manager 9.00 Application CD, and install
ServeRAID Manager Console (Standalone Edition). You need only the Console,
so do not install other components. The system should already have IBM JRE
1.5 or later versions installed.

598 IBMSystems Director Systems Management Guide

 6. Open a Web browser connection to IBM Systems Director Server, discover the
system that hosts the RAID adapter, request access, and collect inventory. The
’ServeRAID Manager Level 1 Agent’ provides inventory and events support.
ServeRAID Manager can now be launched as an External Storage Application
or from the Actions menu of a server of the system that hosts the RAID
adapter.
7. When the ServeRAID Manager Console (Standalone Edition) is launched 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 secondary storage devices and their connectivity to your network.

To launch an external storage management application for a given resource,

perform the following steps:
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 DS4000 Storage Manager for IBM DS3200,
DS3400, and DS4000 devices.
v Click Actions → Launch IBM DS6000 Storage Manager for IBM DS6000
devices.
v Click Actions → Launch ServeRAID Manager for Internal RAID controllers.
The external storage application starts, but you can perform only those tasks
related to the chosen resource.
3. Login to the application and perform 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 is the
only way to launch the IBM TotalStorage Productivity Center.

Requirements for IBM TotalStorage Productivity Center

These requirements must be met when using IBM TotalStorage Productivity Center
with IBM Systems Director.

IBM TotalStorage 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 TotalStorage Productivity Center in an untargeted fashion (for

example, from the External Storage Application page), IBM TotalStorage
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 TotalStorage Productivity Center Web site:
www-03.ibm.com/systems/storage/software/center/.

Chapter 13. Managing and configuring storage 599

 Requirements for IBM DS Storage Manager for DS4000
These requirements must be met when using IBM DS Storage Manager for DS4000
with IBM Systems Director.

IBM DS Storage Manager for DS4000 must be:

1. Version 9.23 to version 10
2. Launched from one of these operating systems: Windows, AIX, or Linux

IBM DS Storage Manager for DS4000 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 for DS4000 is used for DS4000, DS3200 and DS3400 disk
systems.

If you try to invoke IBM DS Storage Manager for DS4000 and it is not found, you
will see a page with installation instructions.

For more information, see the IBM DS Storage Manager for DS4000 Web site:
www.lsi.com/storage_home/products_home/external_raid/
management_software/smis_provider/index.html?remote=1&locale=EN

Requirements for IBM System Storage Manager for DS6000

These requirements must be met when using IBM System Storage Manager for
DS6000 with IBM Systems Director.

IBM System Storage Manager for DS6000 must be:

1. Version 5.2 or later
2. Launched from Windows for an untargeted launch. This is because IBM System
Storage Manager for DS6000 runs only from Windows.

Automatic installation is not supported.

For launching IBM System Storage Manager for DS6000 in an untargeted fashion
(for example, from the External Storage Application page), IBM System Storage
Manager for DS6000 must be installed on the same system that is running the
client browser session (the browser used to connect to IBM Systems Director).

Targeted launch of IBM System Storage Manager for DS6000

For a targeted launch of IBM System Storage Manager for DS6000:

1. Launch from any operating system with a Web browser.
2. IBM System Storage Manager for DS6000 must be installed with IBM Systems
Director, but IBM System Storage Manager for DS6000 does not have to be
installed on the same system as the client browser.
3. The IBM DS6000 storage devices must have been discovered using IBM
Systems Director.

For more information, see the IBM System Storage Manager for DS6000 Web site:
www.ibm.com/systems/support/supportsite.wss/supportresources?taskind=2
&brandind=5000033&familyind=5329497

600 IBMSystems Director Systems Management Guide

 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.

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 Manage tab of
the Welcome 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. Discovery and inventory collection must be run before you can
display storage systems. The Storage Management Summary page is divided into
these areas:
Capacity Summary
A pie chart represents your disk capacity in each of these three categories.
Total available capacity
Number of GB of disk space that can be used to create volumes
and assign them to systems.
Total usable capacity
Number of GB of disk space after RAID formatting is performed.
This is the total effective capacity available after RAID overhead.
Usable capacity represents the total storage array or storage pool
space that could be used to create volumes. Initially, when a
storage array or pool is created, the usable and available capacity
are the same. As volumes are created from the total usable
capacity, the amount of available capacity decreases. The usable
capacity is a measurement of the current quantity of usable
storage. This can be used to estimate how much storage might be
required when making technology upgrades.
The capacity measurement is a snapshot created when inventory is
collected on the storage arrays. Inventory collection can be

Chapter 13. Managing and configuring storage 601

 configured to run on a schedule to periodically update the capacity
information if storage volumes and pools are created after the
initial inventory collection.
Total raw capacity
Number of GB of physical disk space. This number can also be
used to estimate storage requirements when making technology
upgrades.
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 usable capacity and Total available capacity is
not included in the Capacity Summary for these storage devices.
Storage tasks
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 total capacity, number of
disk drives, and number of systems. 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.

602 IBMSystems Director Systems Management Guide

 BladeCenter Storage
Storage accessible to all of your IBM BladeCenter systems.
Specifically, this is IBM BladeCenter S storage being managed by
an IBM SAS Controller Module.
From IBM Systems Director, IBM 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 IBM
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.

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 Navigate Resources. The Navigate Resources 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
systems is displayed.
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.

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.

Chapter 13. Managing and configuring storage 603

 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.

Note: For more information about navigating and working with tables in IBM
Systems Director Web interface, see “Table navigation in IBM Systems Director.”

To display the current configuration for a given system, complete the following
steps:
1. Click Navigate Resources. The Navigate Resources page is displayed.
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.

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.

Note: For more information about navigating and working with tables in IBM
Systems Director Web interface, see “Table navigation in IBM Systems Director.”

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.

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.

When using the System Status and Health summary, these areas are of interest
with respect to storage devices, and characteristics that are unique to storage
systems:

604 IBMSystems Director Systems Management Guide

 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 Welcome. The Welcome
page is displayed.
2. On the Welcome page, click the Manage tab. A list of available summary
pages is displayed.
3. On the Manage 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 there are none present, use this page 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.

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:

Chapter 13. Managing and configuring storage 605

 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.

Managing storage in real-time

You can manage storage systems in real-time, without the use of 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 or System x systems.
v Integrated RAID Controllers
v ServeRAID MR Controllers
v IBM 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.

606 IBMSystems Director Systems Management Guide

Related tasks
“Configuring the SMI-S provider for the IBM BladeCenter S SAS RAID Controller
Module” on page 587

Managing IBM BladeCenter 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 IBM BladeCenter or System x 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 discovered, unlocked, and configured.

To manage storage devices attached to an IRC, complete the following steps:

1. From any area that displays the IBM BladeCenter or System x system and its
attached storage devices, such as Navigate Resources, 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.

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
IBM BladeCenter Integrated RAID Controllers and their attached storage devices″
in Related Links at the bottom of this page.

The IBM BladeCenter or System x 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 discovered, unlocked, and configured.

To manage storage devices attached to a ServeRAID MR Controller, complete the

following steps:
1. From any area that displays the IBM BladeCenter or System x system and its
attached storage devices, such as Navigate Resources, select the system or the
operating system that hosts the ServeRAID MR Controller.
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 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.

Chapter 13. Managing and configuring storage 607

 5. Use the page to view long running tasks such as rebuilding pools and
initializing drives.

Managing IBM 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
management tasks for the attached devices.

The IBM BladeCenter 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. 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 IBM BladeCenter 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.
3. View the contents of this page and perform any necessary tasks associated with
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.

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
management tasks for the attached devices.

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 provider has one of these names:
v PlatformAgentSubagent IBM BladeCenter SAS RAID Controller Module 6.1.0
Linux
v PlatformAgentSubagent IBM BladeCenter SAS RAID Controller Module 6.1.0
Windows
2. The IBM BladeCenter chassis must be discovered and unlocked.
3. The attached SAS switch must be discovered and unlocked.

To manage storage devices attached to a SAS RAID Controller Module, complete

the following steps:

608 IBMSystems Director Systems Management Guide

 1. From any area that the IBM BladeCenter system and its attached storage
devices are displayed, such as Navigate Resources, 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.
4. Click Actions → System Configuration → Set Date and Time. A page used to
set the date and time on the selected resource 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 Device Log to display logging information.
v Click Physical Resources to display attached physical resources.
7. View the displayed pages and perform all necessary tasks.
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 Navigate Resources, 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.
12. Click Actions → System Configuration → Set Date and Time. A page used to
set the date and time on the SAS switch is displayed.
13. View the contents of this page and set the date and time if necessary.
14. 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.
v Click Error Counters to view error counts and status messages.
v Click Physical Resources to display attached physical resources.
15. View the displayed pages and perform all necessary tasks.

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.

Note: For more information about navigating and working with tables in IBM
Systems Director Web interface, see “Table navigation in IBM Systems Director.”

Chapter 13. Managing and configuring storage 609

 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.

Note: For more information about navigating and working with tables in IBM
Systems Director Web interface, see “Table navigation in IBM Systems Director.”

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.

Note that a storage volume is similar to a logical volume.

610 IBMSystems Director Systems Management Guide

 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:
1. Click Navigate Resources. The Navigate Resources 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
systems is displayed.
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).

Managing storage volumes in real time

You can create and delete storage volumes in real time. These changes are applied
immediately.

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.

Note that a storage volume is similar to a logical volume.

To delete a storage volume from a server, complete the following steps:

1. Click Navigate Resources. The Navigate Resources page is displayed.
2. Select All Systems. A list of discovered systems is displayed.
3. Select an IBM BladeCenter 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.

Chapter 13. Managing and configuring storage 611

 10. Enter job information, then click OK.
11. Monitor the job to ensure that it completes and review any error messages.

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.

Note that a storage volume is similar to a logical volume.

You can use these definitions for IBM BladeCenter installations that include
management modules or advanced management modules. The settings provided
might be made by way of the management module, but actually might affect other
components in the IBM BladeCenter environment, such as blade servers. All
settings might not be applicable for the supported components.

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.

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 server from scratch, complete
the following steps:
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.

612 IBMSystems Director Systems Management Guide

 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.

Creating a storage volume from a configuration template:

When creating a storage volume for a IBM BladeCenter 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 IBM BladeCenter 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

Chapter 13. Managing and configuring storage 613

 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:
v RAID 0
v RAID 1
v RAID 5
v RAID 0+1
10. 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
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.

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.

You can use these definitions for IBM BladeCenter installations that include
management modules or advanced management modules. The settings provided
might be made by way of the management module, but actually might affect other
components in the IBM BladeCenter environment, such as blade servers. All
settings might not be applicable for the supported components.

614 IBMSystems Director Systems Management Guide

To configure Internet Small Computer System Interface (iSCSI) components in real
time, complete the following steps:
1. Click Navigate Resources → 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 Config.
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.

Chapter 13. Managing and configuring storage 615

 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.

616 IBMSystems Director Systems Management Guide

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.
17. Verify the information on this page. If anything is incorrect, click Edit to make
changes.
18. Click OK. The Blade Server iSCSI Configuration page is displayed again.
19. Click the next step in the list.

Configuring iSCSI initiator VPD 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 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.

To configure iSCSI initiator DHCP settings, complete the following steps:

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.
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. 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.
6. Type the IP address of the iSCSI initiator in the IP Address field.
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.

Chapter 13. Managing and configuring storage 617

 11. 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
12. Type the password that corresponds to the CHAP ID in the Password field.
13. Type the same password in the Confirm Password field.
14. Click OK. The Initiator VPD page is displayed again.
15. Verify the information on this page. If anything is incorrect, click Edit to make
changes.
16. Click OK. The Blade Server iSCSI Configuration page is displayed again.
17. Click the next step in the list.

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.
8. In the Target 2 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
9. Click OK. The initiator-to-target mappings page is displayed again.

618 IBMSystems Director Systems Management Guide

 10. Verify the information on this page. If anything is incorrect, click Edit to make
changes.
11. Click OK. The Blade Server iSCSI Configuration page is displayed again.
12. Click the next step in the list.

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 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.
8. Verify the information on this page. If anything is incorrect, click Edit to make
changes.
9. Click OK. The Blade Server iSCSI Configuration page is displayed again.
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.

You can use these definitions for IBM BladeCenter installations that include
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:
1. Click Navigate Resources → 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 IBM BladeCenter chassis.
4. Click Actions → System Configuration → Current Configuration. A list of the
current configuration for this IBM BladeCenter chassis is displayed.
5. Select the entry whose Configuration Settings title is: SAS Connectivity
Module Zone Configuration.
6. Click Edit.

Chapter 13. Managing and configuring storage 619

 7. Wait while IBM Systems Director gathers the information from the IBM
BladeCenter hardware. The SAS Connectivity Module Zone Configuration
page is displayed with the current information for this IBM BladeCenter
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 one of the blades to permit access to an External SAS module port, by
clicking on the blade 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. 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 all blades that are to access the RAID subsystem.
e. Click OK.
15. If an I/O module type of SAS Connectivity Module is present:
a. Click the Blades - Disks tab.
b. Choose a blade and click the number below its icon.
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 disks.
e. Click OK.
16. 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 IBM BladeCenter hardware, 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.

620 IBMSystems Director Systems Management Guide

 21. Click Deploy. The SAS Connectivity 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 Save. 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.

Managing storage with configuration templates

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
configuration templates.

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.

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 a template type of .
v Storage Provisioning Configuration for storage volumes
v iSCSI Config for iSCSI devices
v SAN Configuration for SAN configuration mapping
v SAS Connectivity 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.

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 OK when you are
finished.

Chapter 13. Managing and configuring storage 621

 Creating a configuration template for a storage volume
A configuration template containing the definitions for a storage volume defined
on a IBM BladeCenter is created using the configuration manager. One
configuration template can be used to define more than one storage volume.

Note that a storage volume is similar to a logical 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. All settings might not be
applicable for the supported components.

To create a configuration template for a storage volume, complete the following

steps:
1. From the Configuration Summary page, locate the Configuration Tasks pane
and click Create a Template.
2. Choose the appropriate target type.
3. Type and 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 Add volume to template page is displayed.
7. Fill in all necessary volume information.
8. Wait for the process to complete and review all messages.
9. When you are finished, click Save. The Volumes page is displayed, with the
new storage volume in the table.

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.

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 so that when a blade fails, its SAN configuration (stored in the
IBM Systems Director Server) can be copied to the replacement 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.

622 IBMSystems Director Systems Management Guide

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 contain SAN configuration
mapping, you must create one.
Related tasks
“Modifying an existing IBM BladeCenter SAN configuration mapping and saving
the changes to a configuration template” on page 625

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
Systems Director Server.

As part of creating a configuration plan for your IBM BladeCenter, you must
include a SAN Configuration mapping configuration template.

Chapter 13. Managing and configuring storage 623

 Note: If a switch has been configured to use security, the SAN configuration
template cannot be automatically deployed on blade deletion or insertion events.

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. 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:
1. From the Configuration Summary page, locate the Configuration Tasks pane
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.
6. Optional: Click Automatically deploy this configuration template when
notified of a matching resource.
7. Click Continue. The SAN Configuration page is displayed.
8. Select the bays that will have their SAN configuration saved to the IBM
Systems Director Server.
v Select one or more bays.
v Click Select all bays to select all of them.
9. Optional: If you have selected a bay in error, click it again to remove it.
10. Click Save. The Configuration Templates page is displayed with the new
configuration template.
11. Select the new configuration template.
12. 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.
13. 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.
14. 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.

624 IBMSystems Director Systems Management Guide

Related tasks
“Modifying an existing IBM BladeCenter SAN configuration mapping and saving
the changes to a configuration template”

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.

You can use these definitions for IBM BladeCenter installations that include
management modules or advanced management modules. The settings provided
might be made by way of the management module, but actually might affect other
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,

complete the following steps:
1. Click Navigate Resources → 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 IBM BladeCenter chassis.
4. Click Actions → System Configuration → Current Configuration. A list of the
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.

Chapter 13. Managing and configuring storage 625

 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 tasks
“Creating a SAN configuration mapping configuration template for an IBM
BladeCenter system” on page 623

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.

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. All settings might not be
applicable for the supported components.

To configure Internet Small Computer System Interface (iSCSI) components using a

configuration template, complete the following steps:
1. From the Configuration Summary page, locate the Configuration Tasks pane
and click Create a Template.
2. Choose the appropriate target type.
3. Type and Name and Description for the new configuration template.
4. In the Configuration to create a template list, choose iSCSI Config.
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.

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.
626 IBMSystems Director Systems Management Guide
 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.

Chapter 13. Managing and configuring storage 627

 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.
17. Verify the information on this page. If anything is incorrect, click Edit to make
changes.
18. Click OK. The Blade Server iSCSI Configuration page is displayed again.
19. Click the next step in the list.

Configuring iSCSI initiator VPD 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 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.

To configure iSCSI initiator DHCP settings, complete the following steps:

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.
4. Select the type of initiator:

628 IBMSystems Director Systems Management Guide

 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. 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.
6. Type the IP address of the iSCSI initiator in the IP Address field.
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.
11. 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
12. Type the password that corresponds to the CHAP ID in the Password field.
13. Type the same password in the Confirm Password field.
14. Click OK. The Initiator VPD page is displayed again.
15. Verify the information on this page. If anything is incorrect, click Edit to make
changes.
16. Click OK. The Blade Server iSCSI Configuration page is displayed again.
17. Click the next step in the list.

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

Chapter 13. Managing and configuring storage 629

 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.
8. In the Target 2 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
9. Click OK. The initiator-to-target mappings page is displayed again.
10. Verify the information on this page. If anything is incorrect, click Edit to make
changes.
11. Click OK. The Blade Server iSCSI Configuration page is displayed again.
12. Click the next step in the list.

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 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.
8. Verify the information on this page. If anything is incorrect, click Edit to make
changes.
9. Click OK. The Blade Server iSCSI Configuration page is displayed again.
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.

You can use these definitions for IBM BladeCenter installations that include
advanced management modules only. The settings provided might be made by
way of the advanced management module, but actually affect the SAS switch.

630 IBMSystems Director Systems Management Guide

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.

Chapter 13. Managing and configuring storage 631

 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.

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:

1. From the Configuration Summary page, locate the Configuration Tasks pane
and click Create a Template.
2. Choose the appropriate target type.
3. Type and Name and Description for the new configuration template.
4. In the Configuration to create a template list, choose SAS Connectivity
Module Zone Configuration.
5. Click Continue. The SAS Connectivity 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.

632 IBMSystems Director Systems Management Guide

 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. If an I/O module type of SAS RAID Module was selected:
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 to the RAID
subsystem.
d. Repeat this process for all blades that are to access the RAID subsystem.
e. Click OK.
14. If an I/O module type of SAS Connectivity Module was selected:
a. Click the Blades - Disks tab.
b. Choose a blade and click the number below its icon.
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 Connectivity 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.

Chapter 13. Managing and configuring storage 633

634 IBMSystems Director Systems Management Guide
Chapter 14. Managing virtual environments
As you monitor the health of your virtual environment, you can 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.

With IBM Systems Director virtualization manager, you can work with virtualized
environments that are managed by the Hardware Management Console (HMC),
the Integrated Virtualization Manager (IVM), Microsoft Virtual Server, VMware,
and Xen virtualization.

As you monitor the total health of your environment, you might come across
issues that are specific to virtual resources. For example, when health status
indicates a warning or critical state for a virtual server, you can add processors or
memory resources that you have reserved for this situation. When you complete
the task, you can see your virtual server return to a healthy state. Alternatively,
you might be using the topology map view and see a warning or critical status on
a host that is depleting resources. You can take action from within the topology
map view. You might choose to relocate all of the virtual servers on the host to a
more robust host, until you can add more resources to the host.

Virtual systems
This topic provides an overview of the different types of systems that you can
manage using IBM Systems Director virtualization manager.

Platform managers
A platform manager manages one or more host systems and their associated virtual
servers and operating systems.

Here are some examples of platform managers:

v IBM Hardware Management Console (HMC)
v IBM Integrated Virtualization Manager (IVM)
v VMware VirtualCenter

IBM Systems Director does not recognize a managed system as a platform manager
until the managed system has been unlocked. (The padlock icon in the Access
column for a managed system indicates that it is secured.) To request access to the
managed system, right-click the managed system and click Request Access. By
providing a valid user name that has local administrative rights to that managed
system and its password, you can unlock and access the system.

Note: Before you can manage a VMware VirtualCenter platform manager, you
must enter credentials to log in to VMware VirtualCenter server. You can do this
by using the Connect task.

Virtual farms
A virtual farm logically groups like hosts and facilitates the relocation task —
moving a virtual server from one host to another host within the virtual farm.

© Copyright IBM Corp. 1999, 2009 635

 A virtual farm can contain multiple hosts and their associated virtual servers. A
VMware VirtualCenter virtual farm can contain only hosts that are being managed
with the same type of virtualization manager subagent. For example, a virtual farm
that contains a host running virtualization manager subagent for VMware ESX
Server can contain only other hosts that are also running virtualization manager
subagent for VMware ESX Server. When a virtual farm is configured, you can
relocate virtual servers between hosts in the farm.

You use the Create Virtual Farm wizard to group hosts together and enable
specialized capabilities for the virtual servers running on the hosts. You can enable
capabilities such as high availability, workload management, live relocation, and
static relocation. Not all capabilities are supported on all platforms.

IBM Systems Director farms in a VMware VirtualCenter

environment

During discovery, IBM Systems Director identifies a system that is running

VMware VirtualCenter server as a platform manager. Then, virtualization manager
subagent continues the discovery process to identify farms that are in a VMware
VirtualCenter environment. If necessary, you can manually request the discovery of
IBM Systems Director farms after IBM Systems Director has discovered a platform
manager. Alternatively, you can create IBM Systems Director farms for a platform
manager.

IBM Systems Director farms are not identical to farms in VMware VirtualCenter
because IBM Systems Director does not use the hierarchical model that VMware
VirtualCenter uses. VMware VirtualCenter supports collections of farms, which are
referred to as farm groups. This concept enables VMware VirtualCenter to present
farms in hierarchical groups within the VMware VirtualCenter client. However,
IBM Systems Director does not have a farm group concept and does not support
displaying the farm groups in the same type of farm hierarchy. When virtualization
manager subagent creates an IBM Systems Director farm for a VMware
VirtualCenter farm that is a member of one or more farm groups, the name of the
IBM Systems Director farm is displayed, but the hierarchy is not displayed. You
can find the full path that VMware VirtualCenter uses in the Virtualization
Properties. See the Vendor identifier field.

Note: If a farm that is contained within a farm group is discovered and later that
farm group is renamed in VMware VirtualCenter, unexpected behavior can occur
with the IBM Systems Director farm in the IBM Systems Director environment.
This unexpected behavior for the IBM Systems Director farm occurs for all
instances of IBM Systems Director Server that are tracking activity on that IBM
Systems Director farm. After a farm group is renamed, you should disconnect from
the platform manager that contains the IBM Systems Director farm and then
connect again.

The farm type of a IBM Systems Director farm in a VMware VirtualCenter

environment is VMware Virtual Center.

IBM Systems Director farms in other virtualization environments

You can create IBM Systems Director farms for use with other supported
virtualization environments. These IBM Systems Director farms are not defined in
any virtualization application, but exist only in IBM Systems Director.

636 IBMSystems Director Systems Management Guide

 The farm type of a IBM Systems Director farm is undefined until you add a host to
it. Then, the farm type becomes one of the following values:
v HMC
v IVM
v Microsoft Virtual Server
v VMware ESX
v VMware ESX 3.0 or later
v Xen

Hosts
In an IBM Systems Director environment, a host is a system that contains resources
from which virtual servers are constructed.

Hosts can be any of the following systems that are configured for the IBM Systems
Director environment:
v A BladeCenter Chassis
v A system running Microsoft Virtual Server
v IBM® Power Systems that are under the control of an IBM® Hardware
Management Console (HMC)
v An IBM® Power Systems server that is under the control of IBM® Integrated
Virtualization Manager (IVM)
v A system running VMware ESX Server
v A system running VMware ESX Server that is under the control of VMware
VirtualCenter
v A system running Xen Virtualization on a supported Linux operating system

A host can manage multiple virtual servers and their guest operating systems.

Hosts that are in a VMware VirtualCenter environment

After you connect to a VMware VirtualCenter platform manager, IBM Systems

Director creates a virtual farm to represent any farm that exists in the VMware
VirtualCenter environment. IBM Systems Director attempts to match each host that
is managed by a VMware VirtualCenter farm to systems that are currently being
managed by IBM Systems Director. If the host is not already being managed by
IBM Systems Director, it will not be added to the managed inventory, and will not
be displayed as a member of the virtual farm in IBM Systems Director.

When a host is running VMware ESX Server in a VMware VirtualCenter

environment, you can perform IBM Systems Director operations on that host
whether it is locked or unlocked. IBM Systems Director communicates out-of-band
with this system.

IBM Systems Director supports only those hosts that are connected to a system that
is running VMware VirtualCenter server. If a VMware VirtualCenter host is
disconnected, IBM Systems Director removes the host and generates a
Virtualization Manager Farm, Host Removed event. IBM Systems Director does
not discover hosts that are connecting to or are disconnected from a system that is
running VMware VirtualCenter server.

The VMware VirtualCenter client must be installed on the system on which IBM
Systems Director is installed.

Chapter 14. Managing virtual environments 637

 Hosts that are in other virtualization environments

A managed system that is running VMware ESX Server or Microsoft Virtual Server
is not recognized as a host when it is locked. To request access to the host,
right-click the managed system and click Request Access. By providing a valid
user name that has local administrative rights to that managed system and its
password, you can access the system.

(VMware ESX Server 3.0 only) The VMware Virtual Infrastructure Client 2.0 must
be installed on the system where IBM Systems Director is installed.

Virtual servers
A virtual server is associated with a host system. The host must be part of a
virtualization environment that is supported in IBM Systems Director.

A virtual server is the logical equivalent of a physical platform. After IBM Systems
Director discovers a host, it continues the discovery process for all the virtual
servers that are associated with the host. When virtual servers are discovered, they
can be powered on and turned off through IBM Systems Director. In addition, you
can edit resources that are assigned to virtual servers, and relocate a virtual server
from one host to another. You can also create additional virtual servers to meet
your needs.

You can use IBM Systems Director to manage virtual servers that are configured
with one or more virtual disks. IBM Systems Director provides support for several
types of virtual disks, including undoable disks.

(VMware VirtualCenter only) IBM Systems Director does not support or display
virtual server groups, which are collections of virtual servers supported by VMware
VirtualCenter. When virtualization manager subagent creates a virtual server that is
a member of one or more virtual server groups, the name of the virtual server
group is ignored and not included in the name of the virtual server.

(Microsoft Virtual Server only) Microsoft Virtual Server has a virtual server status
called save state; IBM Systems Director refers to this feature as suspending a virtual
server. For information about the save state, see the documentation included with
Microsoft Virtual Server.

Undoable disks
An undoable disk is a type of virtual disk that saves changes to a temporary file
instead of to the virtual disk itself. Changes can be committed when the virtual
machine is turned off.

IBM Systems Director creates virtual servers that contain undoable disks. You can
create and view these virtual servers in IBM Systems Director. IBM Systems
Director supports power operations and relocation for virtual servers that contain
undoable disks.

In IBM Systems Director, each virtual server that has undoable disks can have
PowerON and PowerOFF actions that are used to answer questions from the
associated virtualization application when that virtual server is turned on or
turned off. The available actions vary, depending on which virtualization manager
Subagent is controlling the virtual server:
v (Virtualization manager subagent for VMware VirtualCenter and VMware ESX
Server only) By default, when a virtual server is turned off, changes are written

638 IBMSystems Director Systems Management Guide

 immediately to disk, which is the PowerOFF Commit action. If you configure a
PowerOFF action, but do not configure a PowerON action, then, by default
changes saved in the redo log are applied to disk when the virtual server is
turned on, which is the PowerON Commit action.

Note: PowerON and PowerOFF actions are not supported on VMware ESX
Server 3.0.
v (Virtualization manager subagent for Microsoft Virtual Server only) IBM Systems
Director provides PowerOFF actions only for virtual servers with undoable disks
in Microsoft Virtual Server. To configure PowerON actions, you must use the
Web interface to Microsoft Virtual Server. By default, when a virtual server is
turned off, changes to the virtual disk are saved in a redo log, which is the
PowerOFF Keep action.

For detailed information about the undoable disk implementation for a

virtualization application, see its included documentation.

Guest-operating-systems
A guest-operating-system represents an operating system that is running on a virtual
server on which Common Agent is installed. A guest-operating-system is a
particular type of managed system.

The standard IBM Systems Director discovery process for managed systems can
discover guest operating systems. However, if a guest operating system is not
running Common Agent, it is not recognized as a guest-operating-system object in
IBM Systems Director.

Virtualization groups
IBM Systems Director organizes logical sets of resources into groups. Virtualization
manager provides a set of default or predefined groups for virtual resources.

The following table lists the names and descriptions of the groups provided by
virtualization manager.
Table 37. Virtualization manager groups
Group
Virtualization Groups
Platform Managers
Platform Managers and Members
Hosts
Virtual Servers
Virtual Servers and Hosts
Guest Operating Systems
Virtualization Systems
Virtual Farms
Description
Groups for managing virtualization
Systems capable of managing hosts or farms
Platform managers and their hosts or farms
Systems capable of hosting virtual servers
Virtual servers
Virtual servers and their hosts
Operating systems running on virtual
servers
Systems with virtualization capabilities,
attributes, or relationships
Virtual farms

Chapter 14. Managing virtual environments 639

Viewing the virtualization manager summary
You can view a summary of the resources managed by virtualization manager and
the status of those virtual resources. You can also access common management
tasks for managing your virtual resources. Note that information on the
virtualization manager summary page is refreshed automatically when there are
any changes.

To view the virtualization summary, complete the following steps:

1. In the IBM Systems Director navigation area, click Welcome.
2. On the Welcome page, click Manage, scroll to the virtualization manager
portion of the page, and click the Virtualization Manager section heading. The
virtualization manager summary is displayed.
3. View the Status section. This section provides the following information:
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
virtual resources:
– Virtual servers and hosts
– Virtual farms
– Relocation plans
4. View the Manage section. This section provides the following information:
v The number of hosts and virtual servers
v The number of virtual farms
v Links to the following tasks that you can use to create and relocate virtual
resources:
– Create virtual server
– Create virtual farm
– Relocate virtual servers
5. View the Setup and Configuration section. This section provides links to the
following tasks that you can use to get started with virtualization manager:
v Set up virtualization manager
v System discovery
v Install the virtualization manager plug-in on agents

640 IBMSystems Director Systems Management Guide

Viewing resources in virtualization perspectives
You can use basic topology perspectives to view virtual resources. However, you
can use the Virtualization Basic, Virtualization Common, and Virtualization Details
perspectives to isolate virtual resources and drill down further to view additional
details about relationships between virtual resources.

In the Virtualization Basic perspective

You can use the Virtualization Basic perspective to view the same resources found
in the Virtualization Systems group, along with the operating systems running on
the systems and the relationships between the resources.

To view resources in the Virtualization Basic perspective, complete the following

steps:
1. Navigate to a resource whose relationships you want to see in a topology map
view and select it.
2. Click Actions → Topology Perspectives → Virtualization Basic.

In the Virtualization Common perspective

You can use the Virtualization Common perspective to view a common subset of
resources, such as storage pools and network endpoints, along with the basic
resources.

To view resources in the Virtualization Common perspective, complete the

following steps:
1. Navigate to a resource whose relationships you want to see in a topology map
view and select it.
2. Click Actions → Topology Perspectives → Virtualization Common.

In the Virtualization Detail perspective

You can use the Virtualization Detail perspective to view details such as settings,
allocations, and other resources, along with the basic and common resources.

To view resources in the Virtualization Detail perspective, complete the following

steps:
1. Navigate to a resource whose relationships you want to see in a topology map
view and select it.
2. Click Actions → Topology Perspectives → Virtualization Detail.

Viewing resources in the Platform Managers and Members view

You can use the Platform Managers and Members view to see a variety of
information about your platform managers and the hosts or farms that are
controlled by the platform managers. You can view details such as status, IP
address, and descriptions.

Open the Platform Managers and Members view in one of the following ways:
v In the IBM Systems Director navigation area, click Inventory → Views → Platform
Managers and Members.
v In the IBM Systems Director navigation area, click Navigate Resources →
Virtualization Groups → Platform Managers and Members.

Chapter 14. Managing virtual environments 641

Viewing resources in the Virtual Servers and Hosts view
You can use the Virtual Servers and Hosts view to see a variety of information
about your virtual servers and hosts, such as status, IP address, and description.
You can also view CPU utilization for the host or virtual server, as well as the
number of processors and amount of memory that is allocated to your virtual
servers or hosts.

Open the Virtual Servers and Hosts view in one of the following ways:
v In the IBM Systems Director navigation area, click Inventory → Views → Virtual
Servers and Hosts.
v In the IBM Systems Director navigation area, click Navigate Resources →
Virtualization Groups → Virtual Servers and Hosts.

In addition to the columns that are displayed by default in the Virtual Servers and
Hosts view, you might be able to select additional columns depending on your
virtualization environment. For example, you can choose to add the Entitled
Processing Units column in a Power Systems environment.

The following table provides IBM® Power Systems support statements for specific
metrics that are available in the Virtual Servers and Hosts view.
Table 38. Metric support statements for Power Systems managed by Hardware
Management Console or Integrated Virtualization Manager
CPU Utilization Entitled
Virtual system % Processors Memory (MB) Processing Units
HMC host Yes2 Yes Yes No
2 1
HMC virtual Yes Yes Yes Yes2
server
IVM host Yes2 Yes Yes No
2 1
IVM virtual Yes Yes Yes Yes2
server
Platform No No No No
manager
1
Metric information will display only if all processors are running in shared mode. If one
or more processors is running in dedicated mode, the metric will report no data available.
2
No data available is reported if the virtual server (logical partition) processor is configured
to run in dedicated mode, or if a host contains a virtual server processor configuration in
dedicated mode. No data available is also reported if the system is powered off.

Viewing virtualization properties

In addition to viewing the properties listed on the main properties view for a
selected resource, you can see additional properties that are specific to virtual
resources.

To see virtualization properties, complete the following steps:

1. Navigate to a resource whose properties you want to see and select it.
2. Click Actions → Properties.
3. On the General page, click Virtualization Properties (under Additional
Properties) in the upper-right corner of the page.

642 IBMSystems Director Systems Management Guide

 Note: Virtualization Properties is displayed only for resources that provide
virtualization services.

The virtualization properties displayed vary, depending on the resource you

selected.

The Virtualization Properties page lists properties for virtual resources in the
following categories:
Vendor Information
Contains information about the virtualization vendor or the selected
resource in the vendor user interface.
Processor
Contains information about processors such as the number of processors or
processing units.
Memory
Contains information about memory such as memory block size or
available memory.
Disks Contains information about the virtual disks or storage, such as virtual
disk name, virtual disk size, and virtual disk location, for example, the
Virtual I/O Server that is managing the disk in a Power Systems
environment.

Note: Virtual disk size information is not available for VMware ESX Server
2.5.x hosts, VMware VirtualCenter 1.4.x hosts, or Microsoft Virtual Server
hosts that are running IBM Systems Director Virtualization Manager Agent
for Microsoft Virtual Server version 1.2.
Devices
Contains information about devices, such as optical device name and
optical device location. For the Hardware Management Console (HMC)
and Integrated Virtualization Manager (IVM), only optical devices are
supported.
Network
Contains information about the network, such as virtual Ethernet adapters
allocated to the virtual server, and the virtual networks to which the
adapters are connected.
Additional Information
Contains additional information.

Configuring virtual resources

Use this topic to complete configuration steps that might be required in order to
manage your virtual environment.

Configuring Power Systems platform managers

To enable IBM Systems Director to manage IBM® Power Systems platform
managers, you must perform several steps on the Hardware Management Console
(HMC) or the Integrated Virtualization Manager (IVM).

Configuring the HMC

Perform the following configuration steps on the Hardware Management Console
(HMC).

Chapter 14. Managing virtual environments 643

 Setting up user access to the HMC:

Create users on the Hardware Management Console (HMC) with the required
authorities to ensure that users can request access to an HMC from IBM Systems
Director and perform tasks for managing the HMC. There are three HMC user
roles that you can create: hmcsuperadmin, hmcoperator, and hmcviewer.

To request access to an HMC from IBM Systems Director, you must have a user
account on the HMC. When you request access using an HMC user ID and
password, the role associated with the HMC user determines the tasks that are
available in IBM Systems Director for all IBM Systems Director users.

For example, if you request access using an HMC user with the hmcviewer role,
the only IBM Systems Director task that will be available to you is viewing
resource utilization data. You might want to request access in IBM Systems
Director using an HMC user with a higher level of authority, such as hmcoperator,
so that more tasks are available in IBM Systems Director.

An IBM Systems Director super administrator must assign privileges to

administrators before an administrator can access any IBM Systems Director tasks.

The following table describes the IBM Systems Director tasks and the HMC user
roles necessary to perform the tasks.
Table 39. IBM Systems Director tasks and required HMC user roles
IBM Systems
Director tasks HMC user roles
hmcsuperadmin hmcoperator hmcviewer
View topology and
X X
resource properties
View resource
X X X
utilization data
Inventory discovery X X
Create virtual server X X
Edit virtual resources X X
Delete virtual server
X X
permanently
Power management X X
Relocation X X

To learn about creating the HMC users, see the Operations Guide for the Hardware
Management Console and Managed Systems in one of the following information center
topics:
v ″9406-MMA (IBM® System i® 570)″
v ″PDF files for the 9117-MMA (IBM® Power 570)″
Related reference
9406-MMA (IBM System i 570)
PDF files for the 9117-MMA (IBM Power 570)

Enabling the HMC for remote command execution:

644 IBMSystems Director Systems Management Guide

Enable the Hardware Management Console (HMC) for remote command execution
so that IBM Systems Director can communicate with the HMC.

To enable or disable remote commands, you must be a member of one of the

following roles:
v super administrator
v service representative

To enable the HMC for remote command execution, complete the following steps:
1. In the HMC Navigation Area pane, expand the affected HMC and expand
HMC Management.
2. Open the Remote Command Execution task from the HMC Management work
pane.
3. From the Remote Command Execution window, select Enable remote
command execution using the ssh facility.
4. Click OK to proceed.

Setting the HMC to collect resource utilization data for managed systems:

Use this procedure to set the Hardware Management Console (HMC) to collect
resource utilization data for any of the managed systems that it manages.

To set the HMC to collect resource utilization data, you must be a super
administrator or operator.

When you set the HMC to collect resource utilization data for a managed system,
the HMC collects utilization data for memory and processor resource. The HMC
collects utilization data into records called events. Events are created at the
following times:
v At periodic intervals that you set
v When you make system-level and partition-level state and configuration changes
that affect resource utilization
v When you start up, shut down, and change the local time on the HMC

To set the HMC to collect resource utilization data, follow these steps:
1. In the navigation area, expand Systems Management.
2. Expand Servers.
3. In the corresponding systems table, select the servers that you want to enable
for collecting utilization data.
4. In the task area, expand Operations, and then expand Utilization Data.
5. Click Change Sampling Rate.
6. In the Change Sampling Rate window, select the sampling rate that you want
to use for the systems you have selected. You can choose from the following
options:
v 30 seconds
v 1 minute
v 5 minutes
v 30 minutes
v 1 hour

Chapter 14. Managing virtual environments 645

 Configuring the IVM
Perform the following configuration steps on the Integrated Virtualization Manager
(IVM).

Setting up user access to the IVM:

Create users on the Integrated Virtualization Manager (IVM) with the required
authorities to ensure that users can request access to an IVM from IBM Systems
Director and perform tasks for managing the IVM. There are three IVM user roles
that you can create: padmin, View/Modify, and View Only.

To request access to an IVM from IBM Systems Director, you must have a user
account on the IVM. When you request access using an IVM user ID and
password, the role associated with the IVM user determines the tasks that are
available in IBM Systems Director for all IBM Systems Director users.

An IBM Systems Director super administrator must assign privileges to

administrators before an administrator can access any IBM Systems Director tasks.

The following table describes the IBM Systems Director tasks and the IVM user
roles necessary to perform the tasks.
Table 40. IBM Systems Director tasks and required IVM user roles
IBM Systems
Director tasks IVM user roles
padmin View/Modify View Only
View topology and
X X X
resource properties
View resource
X X X
utilization data
Inventory discovery X X
Create virtual server X X
Edit virtual resources X X
Delete virtual server
X X
permanently
Power management X X
Relocation X X

To learn about creating the IVM users, see ″Creating IVM user accounts.″
Related reference
Creating IVM user accounts

Enabling the IVM for remote command execution:

Enable the Integrated Virtualization Manager (IVM) for remote command

execution by starting secure shell (ssh) one time. The ssh service is subsequently
started whenever you reboot the IVM.

To enable the IVM for remote command execution, complete the following steps:
1. Connect to the IVM using Telnet or another application.
2. Use the default user ID padmin to log into the IVM.

646 IBMSystems Director Systems Management Guide

3. Determine whether the IVM is enabled for remote command execution by
default.
On the Virtual I/O Server command line, type the following command:
lsnetsvc ssh

If remote command execution is enabled, you have completed this task.

Output similar to the following code will be displayed:
Subsystem Group PID Status
sshd ssh Process_ID active

where Process_ID is the identification number assigned to the process.

If remote command execution is not enabled, continue with the next step.
Output similar to the following code will be displayed:
Subsystem Group PID Status
sshd ssh Process_ID inoperative

where Process_ID is the identification number assigned to the process.

4. Type the following command:
ioscli startnetsvc ssh

After you start the ssh service, it will continue running until you issue a command
to stop it.

Starting Common Information Model (CIM) server on the IVM:

Start the cimserver service one time. The cimserver service is subsequently started
whenever you reboot the Integrated Virtualization Manager (IVM) managed object.

To start the cimserver service on the IVM, complete the following steps:
1. Connect to the IVM using Telnet or ssh.
2. Use the default user ID padmin to log into the IVM.
3. On the Virtual I/O Server command line, type the following command:
ioscli startnetsvc cimserver

After you start the cimserver service, it will continue running until you issue a
command to stop it.

Configuring credentials for the FSP CIM Proxy:

To enable power on and power off tasks for an IVM-managed Power Systems
server or a standalone Power Systems server, you must configure credentials for
the Flexible Service Processor (FSP) Common Information Model (CIM) Proxy.

Ensure that you have installed the FSP Proxy extension and the IBM Cluster
Systems Management utilities.

To configure the FSP CIM Proxy and enable power on and power off tasks for the
Power Systems server, complete the following steps:
1. In the IBM Systems Director navigation pane, click Navigate Resources to
locate the Power Systems server for which you want to enable power
management tasks; the system will display partial access if the credentials are
not configured.
2. Right-click the Power Systems server and select Security → Configure Access.

Chapter 14. Managing virtual environments 647

 3. On the Configure Access page, click the CIM Proxy Access entry.
4. Click Configure Credentials. The Configure Credential Wizard is displayed.
a. If the Welcome page is displayed, click Next.
b. On the Credential Type page, select the User ID and Password credential
type and click Next.
a. On the Credential Detail page, specify HMC for the User ID and the
associated HMC User ID password. Click Next.

Note: If you do not know the password for the HMC User ID, you can log
in to the Advanced System Management interface on the FSP with the
Admin User ID and change the password for the HMC User ID. You can
find the IP Address for the FSP on the IBM Systems Director Configure
Access page in the CIM Proxy Access row under the Access Information
heading. Use the Login Profile → Change Password task and select to
change the HMC User ID.
a. On the Summary page, click Finish.
5. When you have completed the Configure Credential Wizard, click Apply
Credentials. When the apply credentials request is complete, the CIM Proxy
Access point should display OK in the Access column.
6. If you return to Navigate Resources and right-click on the Power Systems
server, you should now see the option for Power On/Off → Power Off Now or
Power On/Off → Power On depending on the current power state of your
server.

Note: Unless you have configured credentials for each Remote Service Access
Point, you will continue to see Partial access for the Power Systems server.
Related reference
Preparing to install IBM Systems Director Server on AIX
Preparing to install IBM Systems Director Server on AIX

Configuring storage resources

To use IBM Systems Director virtualization manager to relocate virtual servers
from one host to another, you must have a shared storage area network (SAN)
configured.

Relocation requirements
Before you start a virtual server relocation, ensure that you meet the relocation
requirements.
v Relocation of virtual servers is possible only between hosts within the same
virtual farm.
v Both the source and target host must have access to a shared storage area
network (SAN).

Note: For Xen relocation, the virtual server image must be available on a shared
storage volume, with that volume mounted by both the source and target host.
v Both the source and target host must have access to a shared communications
network.
v The target host must have enough memory to support the virtual server.

648 IBMSystems Director Systems Management Guide

 Note: Additionally, for Xen, the source host must have memory available that is
equal to or greater than the virtual server or virtual servers that you want to
relocate.
v The target host must support the configuration version of the virtual server.
v Relocation of clustered virtual servers is not supported.
v Relocation of virtual servers that are suspended or in a transition state is not
supported.

Note: Additionally, for Xen, the virtual server cannot be in an offline or paused
state.
v Source and target hosts must have a virtual network device with the same label.

Note: For Xen, the bridge must have the same name on both the source and
target hosts.
v Virtual servers to be relocated cannot be connected to a removable device such
as a CD drive or diskette drive.
v The version of a configuration file for a virtual server must be supported by the
virtualization application with which the virtualization manager subagent
communicates. Otherwise, the virtual server cannot be relocated.
v (IBM® Power Systems only) To relocate a virtual server, ensure that you meet the
minimum virtualization software requirements for the HMC and the IVM.
IBM® Power Systems relocation leverages Live Partition Mobility functionality, a
component of the PowerVM™ Enterprise Edition hardware feature. To utilize the
relocation functionality in IBM Systems Director, you must meet the
requirements described in the “Live Partition Mobility” documentation. For
more information, see the preparation sections in the “Moving the mobile
partition using the HMC” or “Moving the mobile partition using the Integrated
Virtualization Manager” topics.

For further information about virtual server relocation and potential restrictions for
a specific virtualization application, see its included documentation.
Related concepts
Live Partition Mobility
Related tasks
Moving the mobile partition using the HMC
Moving the mobile partition using the Integrated Virtualization Manager
“Relocating a virtual server” on page 682
Related reference
Virtualization software supported by IBM Systems Director

Enabling static relocation for Microsoft Virtual Server hosts

If you want to use static relocation for virtual servers that are associated with
Microsoft Virtual Server hosts, you must complete extra steps to account for
volumes in these environments.

A volume is a discrete unit of storage on disk, tape or other data recording medium
that supports some form of identifier and parameter list, such as a volume label or
input/output control.

Notes:

Chapter 14. Managing virtual environments 649

 1. A volume should be mounted at only one mount point on the source host. A
volume mounted at multiple mount points is not supported.
2. Make sure that the volume that contains the virtual server to be relocated does
not contain any files that are not related to the virtual server. If the volume
contains any files that are not related to the virtual server, everything in the
volume will become inaccessible as soon as the volume is dismounted.
3. When relocating multiple virtual servers on one volume, the relocation
operation succeeds only when all virtual servers on the same volume are
successfully relocated. The operation fails when any of the virtual servers on
the same volume fail to be relocated. In that case, all virtual servers on the
volume are registered again to the source host.
4. Relocation is supported on primary partitions only.

Complete the following steps to perform static relocation for virtual servers that
are associated with Microsoft Virtual Server hosts:
1. Create a volume on the storage area network (SAN). Make sure that the
volume you create is large enough to hold the virtual server.
2. Mount the volume at the source host.
3. Make sure that the destination host can access the volume as initialized or
formatted. If not, the destination host may need to be restarted. However, do
not mount the volume at the destination host.
4. Create a virtual server on the source host and put it on this volume.
5. Create relocation tasks for the virtual server.

Managing host systems

Use IBM Systems Director to run the Enter Maintenance Mode and Exit
Maintenance Mode tasks on your VMware ESX host systems. You can also start
and stop the virtualization service on a host in a Microsoft Virtual Server virtual
farm.

Entering maintenance mode

You can specify that certain hosts be in maintenance mode so that you can perform
service tasks on the host.

For VMware ESX hosts managed by VMware VirtualCenter 2.x, all virtual servers
on the host must be powered off to access the maintenance mode task. VMware
ESX hosts that are in maintenance mode cannot be targeted with tasks such as
Create Virtual Server, Power On, or Relocate Virtual Server.

To change a host to maintenance mode, complete the following steps:

1. In the IBM Systems Director navigation pane, click Navigate Resources to
locate the host.
2. Select the host, click Actions from the menu bar, and select Availability → Enter
Maintenance Mode.
3. In the scheduler window, click OK to run the task immediately. You also can
schedule to run this task at a later time.

Exiting from maintenance mode

You can use the exit maintenance mode task to enable VMware ESX Server hosts
that are managed by VMware VirtualCenter 2.x to once again be targeted by tasks
such as Create Virtual Server, Power On, or Relocate Virtual Server.

650 IBMSystems Director Systems Management Guide

 When the service tasks are complete, you can return the host to a fully functional
state. To exit from maintenance mode, complete the following steps:
1. In the IBM Systems Director navigation pane, click Navigate Resources to
locate the host.
2. Select the host. Click Actions from the menu bar, and select Availability → Exit
Maintenance Mode.
3. In the scheduler window, click OK to run the task immediately. You also can
schedule to run this task at a later time.

Starting the virtualization service on a host

To manage the hosts within a Microsoft Virtual Server virtual farm, the
virtualization service must be started. Although the virtualization service is started
by default, you can use these instructions to restart the virtualization service, if
necessary.

To start the virtualization service on a single host or on all hosts that are associated
with one virtual farm, complete the following steps:
1. In the IBM Systems Director navigation area, click Navigate Resources.
2. Navigate to the resource at which you want to start the virtualization service:
either a single host, or to the virtual farm that contains the hosts.
3. Select the host or virtual farm, click Actions from the menu bar, and select
System Configuration → Start Virtualization Service.
4. In the scheduler window, click OK to run the task immediately. You also can
schedule to run this task at a later time.

Stopping the virtualization service on a host

After you have completed the tasks on the hosts within a Microsoft Virtual Server
virtual farm, you can stop the virtualization service.

To stop the virtualization service on a single host, or on all hosts that are
associated with one virtual farm, complete the following steps:
1. In the IBM Systems Director navigation area, click Navigate Resources.
2. Navigate to the resource at which you want to stop the virtualization service:
either a single host, or to the virtual farm that contains the hosts.
3. Select the host or virtual farm, click Actions from the menu bar, and select
System Configuration → Stop Virtualization Service.
4. In the scheduler window, click OK to run the task immediately. You also can
schedule to run this task at a later time.

Managing virtual farms

You can use IBM Systems Director to create and delete virtual farms, to add and
remove hosts from a virtual farm, and to start or stop virtualization services for a
virtual farm. A virtual farm is a logical grouping of hosts and their virtual servers;
it does not represent a physical system.

Adding a host to a virtual farm

You can use IBM Systems Director to add a host to a virtual farm. When hosts and
their associated virtual servers are located within a virtual farm, the virtual servers
can be relocated from one host to another host.

Complete the following steps to add a host to a virtual farm:

Chapter 14. Managing virtual environments 651

 1. In the IBM Systems Director navigation area, expand Availability.
2. Click Virtual Farms.
3. Select the virtual farm to which you want to add a host, click Actions from the
menu bar, and select Add Host. The Add Host window opens.
Based on the type of virtual farm to which you are adding a host, the contents
of the Add Host window will differ:
v If you are adding a host to a virtual farm that is defined in VMware
VirtualCenter, you must designate the host, a user ID for the host that you
are adding, the password, and the port.

Note: If you add a host to a virtual farm that is under the control of
VMware VirtualCenter 2.x, you might need to check the Event Log to
determine the status of the operation.
v If you are adding a host to a virtual farm that is any other type of virtual
farm, you are required only to select the host from a list of available hosts.
4. In the scheduler window, click OK to run the task immediately. You also can
schedule to run this task at a later time.

Creating a virtual farm

If you want to use virtual server relocation functions, you can create a virtual farm,
which is a container within which you can relocate virtual servers between hosts.
A virtual farm can contain multiple hosts and their associated virtual servers.

The Create Virtual Farm wizard will help you group hosts together and define
specialized capabilities for the virtual servers running on the hosts. A virtual farm
has potential for capabilities such as high availability, workload management,
dynamic relocation, and static relocation if the hosts are enabled for these features.

Complete the following steps to create a virtual farm:

1. In the IBM Systems Director navigation area, expand Availability.
2. Click Create Virtual Farm.
3. Follow the instructions in the wizard to create the virtual farm.

Note: If you are creating a VMware VirtualCenter 1.x farm and choose to
specify an optional path on the Capabilities Details page, any directory that
you specify must already exist on the VMware VirtualCenter system. For
example, if you attempt to create an optional path, vcenter/new_farm, the
new_farm directory must already exist in the vcenter/ root directory.
Related concepts
Live Partition Mobility
Related tasks
“Relocating a virtual server” on page 682

Adding capabilities to a host

When you create a virtual farm, you can use the wizard to add only those hosts
that are enabled with the capabilities that you have selected for the farm. If a
specific host is not available for selection in the Create Virtual Farm wizard, you
must add the capability to the host.

In the Create Virtual Farm wizard, you can enable the following capabilities if you
have hosts to add to the farm that are also enabled with these same capabilities:
v High availability with workload management

652 IBMSystems Director Systems Management Guide

 v Live relocation
v Static relocation

The following list describes the requirements for hosts to participate in a specific
capability:
High availability with workload management
High availability with workload management is supported in the VMware
VirtualCenter environment. The VMware VirtualCenter hosts must have
the Common Agent and virtualization manager subagent installed.
VMware VirtualCenter systems must have either VMware High
Availability or VMware Distributed Resource Scheduler enabled.
Live relocation
Live relocation is supported in the VMware VirtualCenter environment, the
Power Systems environment, and the Xen environment. The hosts must be
configured with the correct agent and subagent:
v VMware VirtualCenter hosts must have the Common Agent and
virtualization manager subagent installed.
v Xen hosts must have the Platform Agent installed.
v Power Systems hosts do not require an agent or subagent.
VMware VirtualCenter systems must have VMotion enabled.
Static relocation
Static relocation is supported in all virtualization environments that are
supported by IBM Systems Director. The hosts must be configured with the
correct agent and subagent:
v Microsoft Virtual Server hosts must have the Common Agent and
virtualization manager subagent installed.
v Power Systems hosts do not require an agent or subagent.
v VMware ESX Server hosts must have the Common Agent and
virtualization manager subagent installed.
v VMware VirtualCenter hosts must have the Common Agent and
virtualization manager subagent installed.
v Xen hosts must have the Platform Agent installed.

Note:
v For hosts that are managed by VMware VirtualCenter, you cannot
specify static relocation explicitly. VMware VirtualCenter determines the
type of relocation to use based on the state of the host.

Deleting a virtual farm from IBM Systems Director and

VMware VirtualCenter
You can use IBM Systems Director to permanently delete a virtual farm from both
VMware VirtualCenter and IBM Systems Director.

If you no longer require a virtual farm, use IBM Systems Director to delete the
corresponding virtual farm from VMware VirtualCenter. This action also deletes
the virtual farm from IBM Systems Director. When you complete this task, the
virtual farm cannot be rediscovered and instead must be re-created. Alternatively,
you can remove a virtual farm only from IBM Systems Director.

Chapter 14. Managing virtual environments 653

 Complete the following steps to delete a virtual farm permanently from a platform
manager and delete its corresponding virtualization component from VMware
VirtualCenter:
1. In the IBM Systems Director navigation area, expand Availability.
2. Click Virtual Farms.
3. Select the virtual farm, click Actions from the menu bar, and select Delete
Permanently.

Note: This menu option is available only when the platform manager that
contains the virtual farm to be deleted is online and authenticated.

Removing a virtual farm from IBM Systems Director

If you no longer require a virtual farm, you can remove it from IBM Systems
Director.

Before you remove a virtual farm from IBM Systems Director, note the following
qualifications:
v When a virtual farm that represents a virtualization component in VMware
VirtualCenter is removed from IBM Systems Director, IBM Systems Director does
not remove the corresponding farm from VMware VirtualCenter. Later, if you
decide that you want to manage the virtual farm in IBM Systems Director, you
can rediscover it. Alternatively, you can permanently delete a virtual farm from
VMware VirtualCenter as well as IBM Systems Director.
v For virtual farms that are associated with hosts that are running virtualization
manager subagents for VMware ESX Server or Microsoft Virtual Server, for hosts
that are associated with Xen virtual servers, or for hosts that are under the
control of the IBM® Hardware Management Console (HMC) or Integrated
Virtualization Manager (IVM), you cannot rediscover these virtual farms in IBM
Systems Director; there is no corresponding virtualization component. This same
principle applies for virtual farms that are undefined; a host has not been added
to the virtual farm to define its type.
v You can remove a VMware VirtualCenter virtual farm even if it contains one or
more hosts. You cannot remove an IBM Systems Director virtual farm that is not
in VMware VirtualCenter if it contains one or more hosts.

Complete the following steps to remove a virtual farm from IBM Systems Director:
1. In the IBM Systems Director navigation area, expand Availability.
2. Click Virtual Farms.
3. Select the virtual farm you want to remove, click Actions from the menu bar,
and select Remove.

Editing a virtual farm

After you have created a virtual farm, you can modify some of the attributes of the
virtual farm, add new hosts to the virtual farm, and also remove one or more
existing hosts from the virtual farm with the Edit Virtual Farm task.

Complete the following steps to edit a virtual farm:

1. In the IBM Systems Director navigation area, expand Availability.
2. Click Virtual Farms.
3. Select the virtual farm, click Actions from the menu bar, and select Edit Virtual
Farm.
4. Follow the instructions in the wizard to edit the virtual farm.

654 IBMSystems Director Systems Management Guide

 Note: To add or remove hosts for a VMware VirtualCenter virtual farm, use
the add host or remove host task instead of the edit a virtual farm task.

Removing a host from a virtual farm

You can use IBM Systems Director to remove a host from a virtual farm when you
no longer want it to be organized within that virtual farm.

Complete the following steps to remove a host from a virtual farm:

1. In the IBM Systems Director navigation area, click Navigate Resources.
2. Navigate to the host that you want to remove from a virtual farm.
3. Select the host, click Actions from the menu bar, and select Remove from
Virtual Farm.

Note: This menu option is available only when the platform manager that
contains the virtual farm is online and authenticated.

Starting the virtualization service on a farm

To manage the hosts within a Microsoft Virtual Server virtual farm, the
virtualization service must be started. Although the virtualization service is started
by default, you can use these instructions to restart the virtualization service, if
necessary.

To start the virtualization service on a single host or on all hosts that are associated
with one virtual farm, complete the following steps:
1. In the IBM Systems Director navigation area, click Navigate Resources.
2. Navigate to the resource at which you want to start the virtualization service:
either a single host, or to the virtual farm that contains the hosts.
3. Select the host or virtual farm, click Actions from the menu bar, and select
System Configuration → Start Virtualization Service.
4. In the scheduler window, click OK to run the task immediately. You also can
schedule to run this task at a later time.

Stopping the virtualization service on a farm

After you have completed the tasks on the hosts within a Microsoft Virtual Server
virtual farm, you can stop the virtualization service.

To stop the virtualization service on a single host, or on all hosts that are
associated with one virtual farm, complete the following steps:
1. In the IBM Systems Director navigation area, click Navigate Resources.
2. Navigate to the resource at which you want to stop the virtualization service:
either a single host, or to the virtual farm that contains the hosts.
3. Select the host or virtual farm, click Actions from the menu bar, and select
System Configuration → Stop Virtualization Service.
4. In the scheduler window, click OK to run the task immediately. You also can
schedule to run this task at a later time.

Viewing virtual farms

You can use the Virtual Farms view to access all of your virtual farms in one
location, along with basic information about them. From the virtual farms view
you can also create new virtual farms, and perform management tasks on existing
virtual farms.

Chapter 14. Managing virtual environments 655

 The Virtual Farm view includes the following information about your existing
farms:
v Virtual farm name
v Type of virtual farm (what type of hosts are contained in the virtual farm)
v Number of hosts contained within the virtual farm
v Number of virtual servers contained within the virtual farm
v Whether or not the virtual farm is enabled with the high availability capability

From within the virtual farm view, you can also create new virtual farms, or
perform management tasks on existing virtual farms, such as editing a virtual
farm.

Access the Virtual Farms view in one of the following ways:

v In the IBM Systems Director Server navigation area, click Availability → Virtual
Farms.
v In the IBM Systems Director Server navigation area, click Navigate Resources →
Virtualization Groups → Virtual Farms.
v In the IBM Systems Director Server navigation area, click Welcome. Then click
the Manage tab, and select Virtualization Manager. On the virtualization
manager summary page, locate the Common views heading and click Virtual
farms.

Managing virtual servers

You can use IBM Systems Director to create, delete, edit, and relocate virtual
servers, as well as resume and suspend virtual servers. In addition, you can
perform power operations tasks such as powering on and off virtual servers.

Connecting to a platform manager

Before you can use IBM Systems Director to perform management operations on
systems that are under the control of VMware VirtualCenter or VMware ESX
Server 3.x, you must be connected to the platform manager.

For example, you must enter credentials before you can turn on a virtual server
using IBM Systems Director. Entering credentials logs you into the VMware
management interface for that system. Disconnecting from the platform manager
logs you off of the VMware management interface.

After you have entered credentials, any instance of IBM Systems Director Server in
the environment can access that instance of VMware VirtualCenter server or
VMware ESX Server 3.x. You can continue to enter credentials from any instance of
IBM Systems Director Server in the environment. You can revoke credentials only
from those instances of IBM Systems Director that originally entered credentials.
After credentials are revoked from the last instance of IBM Systems Director Server
that previously entered credentials, no instance of IBM Systems Director Server can
access that instance of VMware VirtualCenter server.

Note: In an IBM Systems Director environment that has multiple management

servers, it is recommended that you use only one management server to manage a
platform manager. Using multiple management servers to manage platform
managers that have authenticated with VMware VirtualCenter causes
unpredictable results.

656 IBMSystems Director Systems Management Guide

 Complete the following steps to connect to a platform manager:
1. In the IBM Systems Director navigation pane, click Navigate Resources to
locate the platform manager that you want to authenticate to the VMware
management interface for that system.
2. Select the platform manager, click Actions from the menu bar, and select
Security → Connect.
3. In the scheduler window, click OK to run the task immediately. You also can
schedule to run this task at a later time.

Disconnecting from a platform manager

When you are connected to a VMware VirtualCenter platform manager or a
VMware ESX Server 3.x platform manager, you can use IBM Systems Director to
perform management operations on systems that are under the control of that
platform manager. If you want to ensure that IBM Systems Director users cannot
access VMware VirtualCenter tasks or VMware ESX Server 3.x tasks, you must
disconnect from the respective platform manager.

When you disconnect from the platform manager, IBM Systems Director deletes
the saved credentials for the platform manager from IBM Systems Director Server.

Complete the following steps to disconnect a platform manager from the VMware
management interface for the system:
1. In the IBM Systems Director navigation pane, click Navigate Resources to
locate the platform manager that you want to disconnect.
2. Select the platform manager, click Actions from the menu bar, and select
Security → Disconnect.
3. In the scheduler window, click OK to run the task immediately. You also can
schedule to run this task at a later time.

Creating virtual servers

You can use IBM Systems Director virtualization manager to create and manage
virtual servers on the host systems in your environment.

Virtual server creation

Virtualization manager includes the ability to create virtual servers on your host
systems by using the Create Virtual Server wizard.

The Create Virtual Server task is available on systems running in the following
virtualization environments:
v Hardware Management Console (HMC)
v Integrated Virtualization Manager (IVM)
v Microsoft Virtual Server
v VMware ESX Server
v VMware ESX Server hosts that are under the control of VMware VirtualCenter
v Xen Virtualization

Typically, the Create Virtual Server task does not install an operating system. You
install the appropriate operating system after the virtual server is created. In the
Xen virtualization environment, a prerequisite for using the Create Virtual Server
wizard is to create an image to be used when the virtual server is created. Then,
when the Xen virtual server creation is completed, the new virtual server is ready
to use.

Chapter 14. Managing virtual environments 657

 Image
A system image is a bootable operating system and additional software in the form
of a single raw image file. IBM Systems Director helps you store and copy system
images to reuse them for creating virtual servers.

IBM Systems Director manages the life cycle of a system image for you.

Although IBM Systems Director manages system images automatically, it is useful

to understand how IBM Systems Director handles and changes your system images
for you.

A system image begins as a master image, which is an image that includes function
but has no identity. For example, a master image has no configuration information
and it is not allocated to any server.

IBM Systems Director uses a master image to create a clone image that you can use
to create a virtual server.

A clone image contains the function that it inherits from a master image. A clone
image can be used immediately to create a virtual server. After you use a clone
image to create a virtual server, the clone image is customized and assigned to that
specific virtual server. If you delete the virtual server, the clone image associated
with the virtual server is also deleted. The clone image that you use to create the
virtual server is the image that the virtual server is configured to boot from.

Xen virtualization supports the following types of image formats:

v partition image
v raw disk image (multi-partitioned)

Image requirements
This topic describes the requirements for using a Xen image to create a virtual
server on a Xen host system.

Ensure that the Xen image, guest operating system, and host system meet the
following requirements:
v The name of the Xen image must include the .img extension.
v The image must not contain a Linux Logical Volume Manager (LVM).
v The image must not contain more than one disk.
v The Linux distribution on the image must match the Linux distribution on the
host system. For example, you must use a SUSE Linux Enterprise 10 image to
create a virtual server on a Xen host running SUSE Linux Enterprise 10.
v The platform of the guest operating system must match the platform of the host
system. For example, if the guest operating system runs on a 32-bit platform, the
host system must also run on a 32-bit platform.
v The kernel on the guest operating system must not be newer than the kernel on
the host system.
v The file system in the image must be supported on the host. For example, if the
image contains an ext3 file system, the version of SUSE Linux Enterprise
installed on the host must support an ext3 file system. Similarly, if the image
contains a ReiserFS, the version of Red Hat Enterprise Linux installed on the
host must support ReiserFS.

658 IBMSystems Director Systems Management Guide

Image repository
An image repository is part of a local or shared file system that is used to store
system images. You can use the system images to create Xen virtual servers.

Xen virtualization supports the following types of image repositories:

v Local
v Network File System (NFS) where NFS is accessible by all corresponding hosts
under the same mount point

You need to create the image repository, either on the local Xen host or within a
shared file system. For more information, see “Creating image repositories for Xen
manually” on page 667.

The Xen host system must be a Platform-Agent managed system. The information
about repositories on a Xen host system will be stored in a configuration file on the
Xen host at the following location: /opt/ibm/director/vm/im/repository.prop

An image repository must be homogenous. That is, it cannot be shared between

hosts running different versions of virtualization software. For example, a host
running SUSE Linux Enterprise Server 10 cannot share a repository with a host
running SUSE Linux Enterprise Server 10 SP1. All the images in a shared
repository must be fully compatible with all the hosts connected to the repository.

Creating images for Xen virtual servers

You can choose from several methods to generate an image to be used when you
create a virtual server on a Xen host. You can use an image creation script to create
a master image, or you can copy an existing Xen virtual server image, clean up
certain settings, and use it to create a new one.

Creating a master image for Xen virtual servers manually:

If you do not create a master image for Xen virtual servers automatically during
the installation process, you can create the master image manually by using an
image creation script. This script is included with the virtualization manager Xen
subagent.

Note: Ensure that the Xen host system has a minimum of 256 MB of memory
available for the image creation process.

To create the master image manually by using the image creation script, complete
the following steps:
1. Ensure that you have completed the steps for installing the virtualization
manager Xen subagent before you proceed with this task.
2. Ensure that you have restarted the machine and booted it from the Xen kernel.
3. The image creation process requires a Network File System (NFS) installation
source that hosts the installation media: SUSE Linux Enterprise Server 10, SUSE
Linux Enterprise Server 10 SP1, or Red Hat Enterprise Linux 5.0. If you do not
already have an NFS installation source, you can set it up on the local Xen host
system or another central location. See the appropriate documentation for
instructions:

Chapter 14. Managing virtual environments 659

 Table 41. Documentation sources for Linux distributions
Operating system
Red Hat Enterprise Linux 5.0
SUSE Linux Enterprise Server 10
Documentation
Red Hat Enterprise Linux Documentation
v For NFS Server Configuration instructions,
see the Red Hat Enterprise Linux 5.0.0
Deployment Guide.
v For instructions to prepare for an NFS
installation, see the Red Hat Enterprise
Linux 5.0.0 Installation Guide.
Note: When you configure the NFS server,
all files and directories must be accessible by
the NFS client, the Xen system on which
you are creating the master image.
SUSE Linux Enterprise Server 10
Documentation

For instructions to set up an installation

server using YaST, see the SUSE Linux
Enterprise Server 10 Installation and
Administration Guide.

Copy the contents of your installation media, such as SUSE Linux Enterprise
Server 10, SUSE Linux Enterprise Server 10 SP1, or Red Hat Enterprise Linux
5.0, to a directory on the NFS server using a descriptive name such
astmp/sources/sles10.

Note: Alternatively, you can use a local installation on the Xen host.
4. Change to the /opt/ibm/director/vm/im directory and run the image creation
script using the following command.

Installation Media Command

Red Hat Enterprise Linux 5.0
SUSE Linux Enterprise Server 10
redhat_inst.py --dest=/var/opt/ibm/vm/images/
vm_master1.img --src=nfs:NFS_Server://
Directory --net=dhcp
suse_inst.py --dest=/var/opt/ibm/vm/images/
vm_master1.img --src=nfs:NFS_Server://
Directory --net=dhcp

Use the following table to understand the variables used when you run the
image creation command.
Table 42. Variables used when you run the image creation command
Variable Description
/var/opt/ibm/vm/images/vm_master1.img The destination at which you want the
generated Xen master image to reside. The
recommended filen ame and location is
/var/opt/ibm/vm/images/
vm_master1.img.
NFS_Server The name of the NFS server, for example,
xen_image. Alternatively, you can specify the
IP address for the NFS server, for example,
192.168.0.1.
Note: Do not specify localhost or 127.0.0.1
for the name of the NFS server.

660 IBMSystems Director Systems Management Guide

Table 42. Variables used when you run the image creation command (continued)
Variable Description
Directory The directory in which you copied the
contents of the installation media, for
example, tmp/sources/sles10 or
tmp/sources/redhat.

The following example shows the image creation command using the sample
variables described in the table.
Table 43. Image creation commands for Linux distributions
Installation Media Command
Red Hat Enterprise Linux 5.0 redhat_inst.py --dest=/var/opt/ibm/vm/
images/vm_master1.img
--src=nfs:xen_image://tmp/sources/redhat
--net=dhcp
SUSE Linux Enterprise Server 10 suse_inst.py --dest=/var/opt/ibm/vm/
images/vm_master1.img
--src=nfs:xen_image://tmp/sources/sles10
--net=dhcp

A series of graphical panels are displayed during the automated process that
creates the image. No action is necessary. Wait for the panels to finish
displaying. The length of time required for the image creation process depends
on your network speed and configuration; the process can take several minutes
to two hours to complete.
5. Verify that the vm_master1.img image was created in the/var/opt/ibm/vm/
images directory.

Note: The images must exist in this directory so that the Create Virtual Server
wizard can retrieve the image to create a virtual server.
6. Discover the Xen host system.

To create a virtual server using the master image, see “Creating a virtual server”
on page 669.

Note: Use the image only with virtualization manager to create a Xen virtual
server. Do not use the image outside of virtualization manager to create a virtual
server.

Read the following information to learn about options you can use when you run
the image creation script and to learn about the settings that are configured in the
master image that the script creates:

You can specify the following options when you run the image creation script.
Specify either the short form or the long form of the option.

Chapter 14. Managing virtual environments 661

 Table 44. Options for the image creation script
Required/
Option Description Optional Default value
-s [d] --src [d] Use [d] as the NFS source for the Required /install
installation media. You must
specify [d] using the following
format: nfs:NFS_Server://
Directory where NFS_Server is
the name of the NFS server and
Directory is the directory into
which you copied the contents of
the installation media.
-d [d] --dest [d] Create the image in the Required /var/opt/
file-backed virtual block device ibm/vm/
(VBD) [d]. [d] can contain the images.
full path for the image file. vm_master.img

-z [d] --size [d] Set the size of the image to [d] in Optional Approximately 2
megabytes. For example, set [d] GB
to 2048 for an image that is
approximately 2 GB in size.
-f --force Overwrite the destination image Optional N/A
if one already exists at that
location.
-c [d] --cache [d] Keep the installation source in Optional N/A
file [d].
-n --net [d] Use [d] to specify the network Required dhcp
parameters. Options are
v dhcp
v local
v ip,mask,gateway,dns where
ip,mask,gateway,dns is a
combination of the IP address,
subnet mask, network
gateway, and DNS server.

-h --help Print this help statement and Optional N/A

exit. This option cannot be used
in combination with any other
options.
-q --quiet The specification for surface Optional N/A
warning level messages for the
command.
-v --verbose The specification for surface Optional N/A
debug level messages for the
command.

The image creation script creates the master image with the following default
settings.
Table 45. Image settings
Configuration Value
Name of the file-backed virtual block device vm_master.img
(VBD)

662 IBMSystems Director Systems Management Guide

Table 45. Image settings (continued)
Configuration Value
Location /var/opt/ibm/vm/images
Size of image Approximately 2 GB
Clock and time zone UTC
Keyboard layout English (US)
Disk partitions For Red Hat Enterprise Linux 5.0:
v xvda1 - 1.7 GB root file system
v xvda2 - 256 MB for swap partition

For SUSE Linux Enterprise Server 10:

Software patterns installed
v hda1 - 258.8 MB for swap partition
v hda2 - 1.7 GB for root file system with
reiserfs
For Red Hat Enterprise Linux 5.0:
v Base package group
v Core package group

For SUSE Linux Enterprise Server 10:

v Server Base System
v Novell AppArmor
v Other packages on which Server Base
System and Novell AppArmor are
dependent
Primary language English (US)
Host and domain name Configured to be set by using Dynamic Host
Configuration Protocol (DHCP)
Password for root user passw0rd
Password encryption Blowfish
Network mode Traditional method without the
NetworkManager Applet
Firewall Enabled; secure shell (ssh) port is open
Network interfaces Ethernet network card; configured with
DHCP
DSL connections, ISDN adapters, and Not configured
modems
VNC remote administration Disabled
Proxy Disabled
CA management Not configured
User authentication method Local
Local users None configured
Printers Not configured

Creating a customized master image for a Xen virtual server manually:

You can use an existing, customized Xen virtual server image as a basis for
creating additional virtual servers on a Xen host system. To enable an existing
virtual server image for use as a master image in IBM Systems Director, you must

Chapter 14. Managing virtual environments 663

 clean up certain settings in the image. For example, the networking configuration
and SSH keys used in the image must be cleared.

Use the following instructions to copy a virtual server image and clean up the
settings in the resulting image manually.

Note: The following instructions require an expert-level knowledge of Linux. You

need to have root privileges to complete these steps. It is also assumed that you
use the bash shell to run these commands.

These instructions are specific to cleaning up the default master image that you
create when you run the image creation script manually. However, you can use the
same overall steps to modify any other virtual server image; the parameters to the
commands might differ depending on the original image that you use.

Create a virtual server, for example, mymaster.img, using the Create Virtual Server
wizard in IBM Systems Director. Customize the virtual server as needed. For
example, you can install and configure applications. When you are finished
customizing your virtual server, complete the following steps to clean your Xen
virtual server so that it can be used as the image to create additional virtual
servers.
1. Shut down and power off the customized Xen virtual server. In IBM Systems
Director Navigate Resources, right-click the virtual server and select Power and
Energy → Shutdown and Power Off.

Important: Shutting down the virtual server is necessary to avoid data

corruption.
2. Make a copy of the mymaster.img image and move it from var/opt/ibm/vm/
domains/mymaster.img to the /var/opt/ibm/vm/images directory. For example,
cp /var/opt/ibm/vm/domains/mymaster.img /var/opt/ibm/vm/images/

Note: mymaster.img is the virtual server you created using the Create Virtual
Server wizard, and have subsequently customized.
3. Mount the mymaster.img image to clean it:
a. Change to any temporary working directory and create a directory called
mnt using the following commands, for example:
cd /tmp
mkdir mnt
b. Determine the available loop devices on your system. To do this, issue one
of the following commands:
v Run the following command:
losetup -a

You might get an output similar to:

/dev/loop0: [0802]:152122 (/var/lib/xen/images/vm1/vm1)
/dev/loop1: [0802]:152127 (/var/lib/xen/images/vm2/vm2)

This output indicates that loop devices 0 and 1 are in use already.
v Run the following command:
cat /proc/mounts

You might get an output similar to:

664 IBMSystems Director Systems Management Guide

 /dev/hda1 on / type reiserfs (rw,acl,user_xattr)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
debugfs on /sys/kernel/debug type debugfs (rw)
udev on /dev type tmpfs (rw)
devpts on /dev/pts type devpts (rw,mode=0620,gid=5)
securityfs on /sys/kernel/security type securityfs (rw)

Check to see if any loop devices are mounted. If a loop device is

mounted, you will see /dev/loopx in the above output where x is the
number of the loop device being used.
For example: if you see a line such as the following, it means that
/dev/loop0 is in use:
/dev/loop0 /mnt iso9660 ro 0 0
Determine two available loop devices using this output. The following
instructions assume that you are using /dev/loop0 and /dev/loop1.
Substitute appropriately depending on the available loop devices in your
system.
c. Associate the loop device, /dev/loop0, to your new master image so that
you can examine the image and determine the partitions that are being used
in mymaster.img:
losetup /dev/loop0 /var/opt/ibm/vm/images/mymaster.img

Command and parameters Description

losetup The Linux command to set up and work
with loop devices.
/dev/loop0 Use loopback device 0.
/var/opt/ibm/vm/images/mymaster.img Name of the new master image.

d. Examine the partition table of the master image, by using the loop device.
Obtain the partition table information by running the following command:
fdisk -l -u /dev/loop0

Command and parameters Description

fdisk Partition table manipulator for Linux.
-l Parameter to list the partition tables for the
specified device.
-u Parameter to display sizes in sectors instead
of cylinders.
/dev/loop0 Display the partition table from the device
/dev/loop0.

This command gives you a table-like output. For example:

Disk /dev/loop0: 2147 MB, 2147484672 bytes
255 heads, 63 sectors/track, 261 cylinders, total 4194306 sectors
Units = sectors of 1 * 512 = 512 bytes

Device Boot Start End Blocks Id System

/dev/loop0p1 * 63 530144 265041 82 Linux swap / Solaris
/dev/loop0p2 * 530145 4192964 1831410 83 Linux

Find the entry that corresponds to the root file system partition. For the
default images created by the image creation script, this is hda2 or the
second row in the partition table. If you created an image with the image

Chapter 14. Managing virtual environments 665

 creation script using the --noauto option and specified a custom partitioning
scheme, find the appropriate row in this table.
In the same row, find the value under the Start column that gives the
starting offset of the root partition. This is typically 530145 for the default
master images. Also, in the table header, you will see the sector size used
for the image given in the Units = sectors of 1 * xx = xx bytes row (or a
similar row). xx is typically 512. Note the values for the starting offset
(start_offset) and the sector size (sector_size).
e. Mount the root partition of mymaster.img to a loop device by issuing the
following command:
losetup -o $((start_offset*sector_size)) /dev/loop1 /dev/loop0

where start_offset and sector_size are the values you noted in the previous
step. For example: losetup -o $((530145*512)) /dev/loop1 /dev/loop0
This command associates the data starting from offset 530145*512 in
/dev/loop0 to /dev/loop1.

Command and parameters Description

losetup Linux command to set up and control loop
devices.
-o $((start_offset*sector_size)) Associate the data starting from this offset to
/dev/loop1. The start_sector and sector_size
values are the values you obtained in the
previous step.
/dev/loop1 Set up the loop device /dev/loop1 to hold
the root partition in the image.
/dev/loop0 Use /dev/loop0 as the source device to
associate to /dev/loop1.

f. Mount the root file system for the mymaster.img image to the ./mnt
directory using the following command:
mount /dev/loop1 ./mnt

Command and parameters Description

mount Linux command to mount a file system.
/dev/loop1 Mount the filesystem from the device,
/dev/loop1.
./mnt Mount the filesystem to the directory ./mnt.

Note: If you get errors while trying to use the loop0 or loop1 devices saying
that the resource is busy, go back to a previous step to determine the
available devices.
g. Clean the networking configuration and ssh keys in the image and set the
YaST configuration tool to run at boot using the following commands:
rm ./mnt/etc/udev/rules.d/30-net_persistent_names.rules
rm ./mnt/etc/ssh/ssh_host_*

Command and parameters Description

rm The Linux command to remove a file.
./mnt/etc/udev/rules.d/30- Indicates the old network configuration files
net_persistent_names.rules to be removed.

666 IBMSystems Director Systems Management Guide

Command and parameters
./mnt/etc/ssh/ssh_host_*
touch
Description
Indicates the location of the old ssh keys to
be removed.
The Linux command to change the
timestamp to the current time.

h. Unmount and detach loop devices using the following commands:

umount ./mnt
losetup -d /dev/loop1
losetup -d /dev/loop0
rmdir ./mnt

Note: Ensure that these devices are unmounted correctly to avoid data
corruption in the new image.

Command and parameters Description

umount Linux command to unmount file systems.
losetup –d Detaches the file or device associated with
the loop device.
rmdir Remove directory.

You now have a new master image created in the /var/opt/ibm/vm/images

directory. Use the Create Virtual Server Wizard to create a new virtual server,
and select the new master image, mymaster.img. When the new virtual server is
first booted, you will be prompted to customize it with authentication,
networking, and other configuration parameters.

Creating image repositories for Xen manually

Virtualization manager defines an image repository in the local file system on the
Xen host system. However, you can create additional image repositories by editing
the image-repository configuration file on the host system.

Creating an image repository for Xen locally:

Create a new image repository for Xen in your local file system by editing the
image-repository configuration file.

To create an image repository for Xen in the local file system, complete the
following steps:
1. On the Xen host system, use a text editor to open the repository.prop file from
the following directory path:
/opt/ibm/director/vm/im/repository.prop
2. Update the repository.prop file as shown in the following example.
This sample code from the repository.prop file indicates that there is a default
image repository in the local file system and gives the location for master
images and clone images:
repository.2.label = "Xen"
repository.2.type = "local"
repository.2.masterPath = "/opt/ibm/director/vm/images/masters"
repository.2.clonePath = "/opt/ibm/director/vm/images/clones"
3. To verify that the image repository was created successfully, complete the
following steps:

Chapter 14. Managing virtual environments 667

 a. In the Web interface, use the View and Collect Inventory task on the Xen
host system. Select Software Images Discovery for the inventory collection
profile.

Note: Before you can collect or view inventory for a resource, you must
discover that resource using System Discovery or Advanced System
Discovery.
b. To view the image repository, use one of the following methods:
v Using the Web interface:
From the View and Collect Inventory task, click View Inventory. Verify
that the specified image repository is displayed in the inventory data list
and table, for example, Xen.
v Using the systems management command-line interface (smcli):
Run the following command on IBM Systems Director Server:
smcli lsresources imagerepository

Verify that the specified image repository is displayed in the output, for
example, Xen.

Creating an image repository for Xen on an NFS:

Create a new image repository for Xen on a Network File System (NFS) by editing
the image-repository configuration file.

Use the following example as a guide for creating a new image repository for Xen
on an NFS. The example consists of the following components:
v NFS share on NFS Server srv.domain.com
v Managed system: Xen host A
v Managed system: Xen host B

Xen host A and Xen host B are both connected to NFS Server srv.domain.com and
share the image repositories located on the NFS.

To create a new image repository for Xen on the NFS, complete the following
steps:
1. Configure an NFS if you have not done so already.
a. On NFS server srv.domain.com, complete the following steps:
1) Update the /etc/exports file as follows:
/images *(rw, sync, no_root_squash)
2) Run the following command to apply the new export:
exportfs -a
3) Create two subdirectories under the exported directory that will hold
master images and clone images, as follows:
mkdir /images/masters
mkdir /images/clones
b. On Xen host system A and Xen host system B, update the /etc/fstab file as
follows:
srv.domain.com:/images /opt/ibm/director/vm/nfs_images nfs defaults 0 0
c. On Xen host A and Xen host B, mount the following:
mount /opt/ibm/director/vm/nfs_images

668 IBMSystems Director Systems Management Guide

2. On Xen host A and Xen host B, use a text editor to open the repository.prop file
from the following directory path:
/opt/ibm/director/vm/im/repository.prop
3. Update the repository.prop file as shown in the following example.
This sample code indicates that there is an image repository on an NFS and
gives the location for master images and clone images:
repository.2.label = "Xen shared NFS"
repository.2.type = "nfs"
repository.2.masterPath = "/opt/ibm/director/vm/nfs_images/masters"
repository.2.clonePath = "/opt/ibm/director/vm/nfs_images/clones"
4. To verify that the image repository was created successfully, complete the
following steps:
a. On the Web interface, use the View and Collect Inventory task on the Xen
host systems. Select Software Images Discovery for the inventory collection
profile.

Note: Before you can collect or view inventory for a resource, you must
discover that resource using System Discovery or Advanced System
Discovery.
b. To view the image repository, use one of the following methods:
v Using the Web interface:
From the View and Collect Inventory task, click View Inventory. Verify
that the specified image repository is displayed in the inventory data list
and table, for example, Xen.
v Using the systems management command-line interface (smcli):
Run the following command on IBM Systems Director Server:
smcli lsresources imagerepository

Verify that the specified image repository is displayed in the output, for
example, Xen.

Creating a virtual server

You can use the Create Virtual Server wizard to create virtual servers on your host
systems. The wizard guides you through the virtual-server creation process.

The Create Virtual Server task is available on systems running in the following
virtualization environments:
v Hardware Management Console (HMC)
v Integrated Virtualization Manager (IVM)
v Microsoft Virtual Server
v VMware ESX Server
v VMware ESX Server hosts that are under the control of VMware VirtualCenter
v Xen Virtualization

The wizard prompts you to provide information such as the name, processing
units, memory, and storage to allocate to the virtual server. The information it
requests is specific to the virtualization environment in which the virtual server is
being created.

The Create Virtual Server task usually does not install an operating system. You
install the appropriate operating system after the virtual server is created.
However, in the Xen virtualization environment, a system image is required to

Chapter 14. Managing virtual environments 669

 complete the Create Virtual Server wizard. Then, when the Xen virtual-server
creation is completed, the operating system is installed and the new virtual server
is ready to use.

To create a virtual server, complete the following steps:

1. In the IBM Systems Director navigation pane, click Navigate Resources to
locate the host.
2. Select the host, click Actions from the menu bar, and click System
Configuration → Create Virtual Server.
3. Complete the instructions in the Create Virtual Server wizard to set up a virtual
server.
4. In the Scheduler window, click OK to run the task immediately. You also can
schedule to run this task at a later time.

Virtual and physical processors:

Use the resources in this section to learn about virtual and physical processors for
Power Systems.

To learn about virtual and physical processors for Power Systems, refer to the
following information:
v For POWER 5 systems, see ″Processors.″
v For POWER 6 systems, see the Logical Partitioning Guide in one of the following
information center topics:
– ″9406-MMA (IBM System i 570)″
– ″PDF files for the 9117-MMA (IBM Power 570)″
Related reference
Processors
9406-MMA (IBM System i 570)
PDF files for the 9117-MMA (IBM Power 570)

Creating a virtual server for Microsoft Virtual Server:

Use the Create Virtual Server wizard for Microsoft Virtual Server to specify a
specific location to create a virtual server.

When you create a virtual server in a Microsoft Virtual Server environment, the
virtual server is created in the following default location: C:\Documents and
Settings\All Users\Shared Documents\Shared Virtual Machines\.

To create a virtual server in a location other than the default location, go to the
Virtual Server Name field, and type the fully qualified path of the location in
which you want to create the virtual server, for example,
C:\MyVirtualServers\VirtualServer1

If the directory does not exist, it will be created.

This concept also applies to a shared storage location such as a storage area
network (SAN). In this scenario, the host system must have a shared drive
associated with the storage location.

670 IBMSystems Director Systems Management Guide

 Deleting image repositories for Xen
You can delete image repositories for Xen by editing the image-repository
configuration file

To delete an image repository for Xen, complete the following steps:

1. On the Xen host system, use a text editor to open the repository.prop file from
the following directory path:
/opt/ibm/director/vm/imagemgr/repository.prop
2. Update the repository.prop file by deleting the image repository.
The following example code from the repository.prop file indicates a default
image repository in the local file system and the location for master images and
clone images. You can delete the image repository by removing or changing the
values in the repository.prop file.
repository.0.label = "Default"
repository.0.type = "local"
repository.0.masterPath = "/var/opt/ibm/vm/images"
repository.0.clonePath = "/var/opt/ibm/vm/domains"
3. To verify that the image repository was deleted, complete the following steps:
a. In the Web interface, use the View and Collect Inventory task on the Xen
host system. Select Software Images Discovery for the inventory collection
profile.

Note: Before you can collect or view inventory for a resource, you must
discover that resource using System Discovery or Advanced System
Discovery.
b. To view the inventory for the Xen host system, use one of the following
methods:
v Using the Web interface:
From the View and Collect Inventory task, click View Inventory. Verify
that the specified image repository is not displayed in the inventory data
list and table.
v Using the systems management command-line interface (smcli):
Run the following command on IBM Systems Director Server:
smcli lsresources imagerepository

Verify that the specified image repository is not displayed in the output.

Creating a virtual disk for Xen

Create new virtual disks on the Xen host system when you want to assign
additional virtual disks to your Xen virtual servers.

To create a virtual disk for Xen, complete the following steps:

1. From a command prompt on the Xen host system, type the following command
and press Enter:
dd if=/dev/zero of=/var/opt/ibm/vm/disks/virtual_disk_name bs=1M
count=size_in_MB

where:
v virtual_disk_name is the name you want to specify for the new virtual disk,
for example, virtualdisk1.dsk.
v size_in_MB is the number of megabytes that you want to specify as the size
for the new virtual disk, for example, 10.

Chapter 14. Managing virtual environments 671

 2. To view the name of the new virtual disk, type the following command and
press Enter:
ls -la /var/opt/ibm/vm/disks/
The name of the virtual disk is displayed in the output.
3. To view and manage the new virtual disk, complete the following steps in the
Web interface:
a. Discover the Xen host system using System Discovery.
b. Click Navigate Resources to navigate to the Xen host system.
c. Request access to the Xen host system. After the view is refreshed, you can
view the new virtual disk.

Deleting a virtual server permanently

If you no longer require a virtual server, you can delete it permanently from its
associated host.

If you perform this task, the virtual server cannot be rediscovered and instead
must be re-created.

You can permanently delete a virtual server from its associated host only when the
virtual server has been powered off.

| Note: The delete virtual server task does not delete the associated disk storage in
| the following environments:
| v Power Systems servers managed by Hardware Management Console or
| Integrated Virtualization Manager
| v Xen virtualization
| v Linux on System z systems running on the z/VM hypervisor

Complete the following steps to delete a virtual server from its associated host:
1. In the IBM Systems Director navigation pane, click Navigate Resources to
locate the virtual server.
2. Select the virtual server, click Actions → System Configuration from the menu
bar, and click Permanently Delete.
3. In the scheduler window, click OK to run the task immediately. You also can
schedule to run this task at a later time.

Editing host resources

You can edit the resources for a host running VMware ESX Server that is under
VMware VirtualCenter control to enable relocation for VMware VirtualCenter
VMotion. You can also edit host resources for an IBM® Power Systems.

For Power Systems that are under the control of the Hardware Management
Console (HMC) or the Integrated Virtualization Manager (IVM), you can edit disk
resources for the host, as well as processor and memory allocations for the virtual
servers that are running on the host.

Note: The edit host resources task might take several minutes to complete for
Power Systems that are managed by the HMC or IVM. Results can be found in the
job log associated with the request.

Complete the following steps to edit host resources:

672 IBMSystems Director Systems Management Guide

 Note: You can also perform this task using the virtualization commands from the
systems management command-line interface. For more information, see
″Virtualization commands.″
1. In the IBM Systems Director navigation area, click Navigate Resources to locate
the host that you want to edit.
2. Select the host, click Actions from the menu bar, and select System
Configuration → Edit Host. The Edit Host Resources window opens.
3. After completing the changes you want to request, click OK.
4. In the scheduler window, click OK to run the task immediately. You also can
schedule to run this task at a later time.

Editing virtual servers

You can edit the virtual resources that are allocated to a virtual server. Depending
on the platform, you can edit resources such as memory, processors, and virtual
disks.

You must power off a virtual server before you can change the values of most
attributes. The following exceptions apply:
v For a VMware VirtualCenter or VMware ESX Server environment and Microsoft
Virtual Server environment, the virtual server can be running when you change
the value of the undoable disk attributes.
v In a Power Systems environment, in which systems are managed by the
Hardware Management Console (HMC) or the Integrated Virtualization Manager
(IVM), the virtual server can be running when you edit memory and processor
allocations.
| v In a z/VM environment with IBM Systems Director VMControl installed, you
| can edit active virtual servers to add and configure the following new
| components: processors, disk storage, and network ports. You can also set the
| CPUAFFINITY and share values for processors.
| When you are editing an active virtual server, you can select how you want the
| changes applied. You can choose to apply the changes in the following ways:
| – To the current session only.
| – To the stored settings that will take effect after the next restart.
| – To both the active settings in the current session and the stored settings that
| will continue to be used after the next restart.

The resources that you are able to edit on a powered off virtual server vary by the
type of virtual server to which the resources are allocated:
v In a VMware VirtualCenter or VMware ESX Server environment, you can set the
memory size, the number of central processing units (CPUs), the virtual disk
type, and the PowerON and PowerOFF action for undoable disks.
If VMware VirtualCenter is using VMware Distributed Resource Scheduler
(DRS) you can choose whether a virtual server can move from its current host,
If VMware VirtualCenter is using VMware High Availability (HA) you can edit
the restart priority.

Note: The PowerOn and PowerOFF actions for undoable disks cannot be set for
VMware ESX Server 3.0.
v In a Microsoft Virtual Server environment, you can set the memory size, the
virtual disk mode, and the PowerOFF action for undoable disks.

Chapter 14. Managing virtual environments 673

 v In a Power Systems environment, you can edit the minimum, maximum, and
assigned processors for virtual servers that are running in both shared processor
mode and dedicated processor mode. You can also edit the virtual or physical
disks that are assigned, the minimum and maximum memory that is assigned,
virtual Ethernet adapters, and the optical devices that are assigned to a virtual
server.
In a Power Systems environment that is managed by the HMC or the IVM, you
can edit the physical I/O slots that are assigned to a virtual server, so that you
can assign non-virtualized I/O devices such as physical storage or Ethernet
adapters. For virtual servers running the IBM i operating system, you can select
a load source and an alternate restart device.
For virtual servers that are powered on and managed by the HMC, you can
choose to change virtual server settings temporarily or permanently. Temporary
changes remain in effect only until you power off the virtual server.

Notes:
– The edit virtual resources task might take several minutes to complete for
Power Systems that are managed by the HMC or the IVM. Check the
job-instance log for status.
– For a Virtual I/O Server, you can edit only memory and processor resources.
v In a Xen environment, you can edit the processors assigned to the virtual server,
the virtual disk assigned, and the minimum and maximum memory available.
| v In a z/VM environment with IBM Systems Director VMControl installed, you
| can edit processors assigned to the virtual server as well as their share values,
| the initial and maximum memory assigned, the storage associated, the networks
| assigned, and the server settings that are specified. The types of virtual server
| storage that you can edit are minidisks, virtual storage disks, temporary disks,
| linked disks, and dedicated disks. However, you cannot increase the size of a
| z/VM minidisk. For server settings on the virtual server you can edit privilege
| classes, options, and IPL statements.

To edit the virtual resources of a virtual server, complete the following steps:

Note: Alternatively, you can perform this task using the virtualization commands
from the systems management command-line interface. For more information, see
″Virtualization commands.″
1. In the IBM Systems Director navigation area, click Navigate Resources to locate
the virtual server that you want to edit.
2. Select the virtual server, click Actions from the menu bar, and select System
Configuration → Edit Virtual Server.
3. In the scheduler window, click OK to run the task immediately. You also can
schedule to run this task at a later time.

Accessing the Xen remote console

Access the Xen console remotely for your Xen virtual servers.

To access a Xen console remotely, complete the following steps:

1. In the IBM Systems Director navigation pane, click Navigate Resources to
locate the Xen virtual server that you want to access remotely.
2. Select the virtual server, click Actions from the menu bar, and select System
Configuration → Remote Access → Launch Remote Console.

674 IBMSystems Director Systems Management Guide

Managing power operations on virtual servers
IBM Systems Director supports power operations that you can perform on virtual
servers.

Note: (Virtualization manager subagent for VMware VirtualCenter only) Even

though a power operation for a virtual server is initiated through VMware
VirtualCenter, if the virtual server contains undoable disks, IBM Systems Director
responds to questions about the power operation. This can be confusing since
VMware VirtualCenter reports that there are questions to answer, but IBM Systems
Director has already answered the questions. You can disregard the questions that
might appear in VMware VirtualCenter. This situation does not occur when you
are using the virtualization manager Agents for VMware ESX Server or VMware
GSX Server.

Managing power operations for a single virtual server

You can complete the following power operations on individual virtual servers:
Power On, Restart Now, Power Off Now, Shutdown and Power Off, Suspend, and
Resume.

The table below describes the power operations that you can perform.

Note: Systems that are controlled by a Hardware Management Console (HMC) do

not have the following power operations available:
v Shutdown and Power Off
v Suspend
v Resume
Table 46. Menu options for power-management operations for virtual servers
Menu option Description
Power Off Now The virtual server is turned off without an orderly shutdown of its guest
operating system. This operation immediately stops all applications that
are in use on that guest operating system.
Power On The virtual server is turned on.
Restart Now The virtual server is restarted immediately, which means that it is
restarted without an orderly shutdown of its guest operating system.
This operation immediately stops all applications that are in use on that
guest operating system.
Resume The virtual server resumes operation and is no longer suspended.
Shutdown and (Virtualization manager subagent for VMware VirtualCenter only) If
Power Off VMware Tools is installed on the guest operating system, this menu
option performs an orderly shutdown of the guest operating system and
then turns off the virtual server. However, if VMware Tools is not
installed on the guest operating system, this menu option will fail.

(Virtualization manager subagent for VMware ESX Server only) If

VMware Tools is installed on the guest operating system, this menu
option performs an orderly shutdown of the guest operating system and
then turns off the virtual server. However, if VMware Tools is not
installed, this menu option will fail.

(Virtualization manager subagent for Microsoft Virtual Server only) If

the guest operating system is a Windows operating system and if
Microsoft Virtual Machine Additions is installed on the guest operating
system, this menu option performs an orderly shutdown of the guest
operating system and then turns off the virtual server.

Chapter 14. Managing virtual environments 675

 Table 46. Menu options for power-management operations for virtual servers (continued)
Menu option Description
Suspend The virtual server remains turned on but is suspended from use.

Only those operations that are applicable to the selected virtual server are
available. For example, if a virtual server is suspended, the only available power
operation is Resume.

Complete the following steps to perform a power-management operation for a

virtual server:
1. In the IBM Systems Director navigation pane, click Navigate Resources to
locate the virtual server.
2. Select the virtual server, click Actions from the menu bar, select Power On/Off,
and select the power action that you want to perform.
3. In the scheduler window, click OK to run the task immediately. You also can
schedule to run this task at a later time.

Powering on all stopped virtual servers

You can use IBM Systems Director to power on all stopped virtual servers on a
host.

The power-on operation applies only to virtual servers that are turned off. It does
not affect virtual servers that are already turned on or suspended.

Complete the following steps to turn on all stopped virtual servers that are
associated with a single host:
1. In the IBM Systems Director navigation pane, click Navigate Resources to
locate the host that contains the virtual servers that you want to power on.
2. Select the host, click Actions from the menu bar, and select Power On/Off →
Power On All Virtual Servers.
3. In the scheduler window, click OK to run the task immediately. You also can
schedule to run this task at a later time.

Resuming all suspended virtual servers

You can use IBM Systems Director to resume the operation of all suspended virtual
servers on a host.

This power operation applies only to virtual servers that are suspended. It does
not affect virtual servers that are turned off or already running.

Complete the following steps to resume the operation of all suspended virtual
servers that are associated with a single host:
1. In the IBM Systems Director navigation pane, click Navigate Resources to
locate the host that contains the virtual servers that you want to resume.
2. Select the host, click Actions from the menu bar, and select Power On/Off →
Resume All Suspended Virtual Servers.
3. In the scheduler window, click OK to run the task immediately. You also can
schedule to run this task at a later time.

Suspending all running virtual servers

You can use IBM Systems Director to suspend all running virtual servers on a host.

676 IBMSystems Director Systems Management Guide

 This power operation applies only to virtual servers that are running. It does not
affect virtual servers that are turned off or already suspended.

Complete the following steps to suspend all running virtual servers that are
associated with a single host:
1. In the IBM Systems Director navigation pane, click Navigate Resources to
locate the host that contains the virtual servers that you want to suspend.
2. Select the host, click Actions from the menu bar, and select Power On/Off →
Suspend All Running Virtual Servers.
3. In the scheduler window, click OK to run the task immediately. You also can
schedule to run this task at a later time.

Powering off all running virtual servers

You can use IBM Systems Director to power off all virtual servers that are running
on a host.

The power-off operation applies only to virtual servers that are turned on. It does
not affect virtual servers that are already turned off or suspended.

Complete the following steps to turn off all running virtual servers that are
associated with a single host:

Important: This operation forces a virtual server to turn off without an orderly
shutdown of its guest operating system. All applications that are in use on that
guest operating system are immediately stopped.
1. In the IBM Systems Director navigation pane, click Navigate Resources to
locate the host that contains the virtual servers that you want to power off.
2. Select the host, click Actions from the menu bar, and select Power On/Off →
Force Power Off All Virtual Servers.
3. In the scheduler window, click OK to run the task immediately. You also can
schedule to run this task at a later time.

Relocating virtual servers

You can use IBM Systems Director virtualization manager to relocate a single
virtual server or all of the virtual servers on a host.

Virtual server relocation

Virtual server relocation is the act of moving a virtual server from one host to
another host. Two types of relocation exist: live relocation and static relocation. The
types of relocation that are available for the system to use are dependent on the
virtualization environment.

Live relocation does not modify the power state of the virtual server throughout the
relocation. For example, if a virtual server is powered on when the relocation
begins, it will remain powered on with guest operating systems available for use
throughout the relocation process. Live relocation is an option in the following
virtualization environments:
v IBM Power Systems that are under the control of the Hardware Management
Console or the Integrated Virtualization Manager
v Virtualization manager subagent for VMware VirtualCenter with VMware ESX
Server hosts
v Xen

Chapter 14. Managing virtual environments 677

 If a virtual server is powered on during static relocation, the relocation operation
powers off the virtual server at the beginning of the relocation process and powers
on the virtual server again when the relocation is complete. Only static relocation
can be used when you are running in one of the following virtualization
environments:
v Virtualization manager subagent for Microsoft Virtual Server
v Virtualization manager subagent for VMware ESX Server

Static relocation:

IBM Systems Director Server supports static relocation of virtual servers when you
are using the virtualization manager subagent for VMware ESX Server or Microsoft
Virtual Server. You can also relocate a Xen virtual server, or a virtual server that is
running on an IBM® Power Systems that is under the control of the Hardware
Management Console or the Integrated Virtualization Manager.

In addition to the general cautions, static relocation requires that these additional
cautions be observed when you are relocating virtual servers:
v Be sure that virtual servers to be relocated are either turned on or turned off. If a
virtual server is turned on at the start of a static relocation, virtualization
manager turns off the virtual server, completes the relocation, and then turns on
the virtual server when the relocation completes.
Before any virtual servers are turned off, the guest operating systems on
relocated virtual servers are shut down in an orderly way. When the virtual
servers are turned on after the relocation, the guest operating systems are
restarted.
v (Virtualization manager subagent for VMware ESX Server only) Secure copy
(scp) must be enabled on all VMware ESX Server hosts that are using
Virtualization manager subagent for VMware ESX Server. This requirement
applies only to VMware ESX Server hosts that are running versions earlier than
VMware ESX Server 3.0 Service Console. Secure copy is not required on hosts
running VMware ESX Server 3.0 Service Console.
v (Virtualization manager subagent for VMware ESX Server only) The access mode
of the shared Virtual Machine File System (VMFS) volume should be public.
v (Virtualization manager subagent for VMware ESX Server only) Make sure that
all VMFS volumes on your managed hosts use volume names, and that the
virtual servers use the volume names for specifying the virtual disks.
v (Virtualization manager subagent for VMware ESX Server only) The virtual
server configuration file should not reside on a VMFS partition. This
requirement does not apply to hosts running VMware ESX Server 3.0 Service
Console.
v (Microsoft Virtual Server hosts only) Extra steps must be completed to account
for volumes in these environments. Specifically, virtual servers on the source
host must be put on a volume on a shared storage area network (SAN) and the
target host must have access to this shared SAN.
v (Microsoft Virtual Server hosts only) Any saved files (from a suspend operation)
and undo disk files must be on shared storage.
v (Virtualization manager subagent for Microsoft Virtual Server only) Relocation of
a virtual server that has the same display name as a virtual server on the target
host is not supported.
v (Virtualization manager subagent for Microsoft Virtual Server only) Relocation of
a virtual server that contains one or more differencing or linked disks is not
supported.

678 IBMSystems Director Systems Management Guide

During a static relocation, loss of network connectivity during virtual server
relocation can cause the virtual server to be inaccessible.

In the VMware VirtualCenter documentation, static relocation is referred to as

migration.

Live relocation:

You can perform live relocation of virtual servers when using the Virtualization
manager subagent for VMware VirtualCenter. You can also relocate a Xen virtual
server, or a virtual server that is running on an IBM® Power Systems that is under
the control of the Hardware Management Console or the Integrated Virtualization
Manager.

Live relocation in a VMware ESX environment: Live relocation for VMware

VirtualCenter is supported only for hosts that are running VMware ESX Server in a
VMware VirtualCenter environment. The guest operating systems on relocated
virtual servers remain available for use; they are not shut down.

VMware VirtualCenter VMotion must be enabled on both the source host and
target host between which you want to perform a live relocation of virtual servers.
You can use VMware VirtualCenter client to enable VMotion for the applicable
hosts. For information about VMware VirtualCenter VMotion requirements, see the
documentation included with VMware VirtualCenter. When using VMware
VirtualCenter 1.3, you can use virtualization manager to set a host attribute that
enables relocation.

Live relocation is not supported for virtual servers that contain undoable disks that
are turned off with the PowerOFF action to keep (that is, save the changes in a
redo log).

During a live relocation, VMware VirtualCenter is sometimes unable to relocate a

virtual server in an active state, as requested.

In the VMware VirtualCenter documentation, live relocation is referred to as

migration with VMotion.

Relocation requirements:

Before you start a virtual server relocation, ensure that you meet the relocation
requirements.
v Relocation of virtual servers is possible only between hosts within the same
virtual farm.
v Both the source and target host must have access to a shared storage area
network (SAN).

Note: For Xen relocation, the virtual server image must be available on a shared
storage volume, with that volume mounted by both the source and target host.
v Both the source and target host must have access to a shared communications
network.
v The target host must have enough memory to support the virtual server.

Note: Additionally, for Xen, the source host must have memory available that is
equal to or greater than the virtual server or virtual servers that you want to
relocate.

Chapter 14. Managing virtual environments 679

 v The target host must support the configuration version of the virtual server.
v Relocation of clustered virtual servers is not supported.
v Relocation of virtual servers that are suspended or in a transition state is not
supported.

Note: Additionally, for Xen, the virtual server cannot be in an offline or paused
state.
v Source and target hosts must have a virtual network device with the same label.

Note: For Xen, the bridge must have the same name on both the source and
target hosts.
v Virtual servers to be relocated cannot be connected to a removable device such
as a CD drive or diskette drive.
v The version of a configuration file for a virtual server must be supported by the
virtualization application with which the virtualization manager subagent
communicates. Otherwise, the virtual server cannot be relocated.
v (IBM® Power Systems only) To relocate a virtual server, ensure that you meet the
minimum virtualization software requirements for the HMC and the IVM.
IBM® Power Systems relocation leverages Live Partition Mobility functionality, a
component of the PowerVM Enterprise Edition hardware feature. To utilize the
relocation functionality in IBM Systems Director, you must meet the
requirements described in the “Live Partition Mobility” documentation. For
more information, see the preparation sections in the “Moving the mobile
partition using the HMC” or “Moving the mobile partition using the Integrated
Virtualization Manager” topics.

For further information about virtual server relocation and potential restrictions for
a specific virtualization application, see its included documentation.
Related concepts
Live Partition Mobility
Related tasks
Moving the mobile partition using the HMC
Moving the mobile partition using the Integrated Virtualization Manager
“Relocating a virtual server” on page 682
Related reference
Virtualization software supported by IBM Systems Director

Enabling static relocation for Microsoft Virtual Server hosts

If you want to use static relocation for virtual servers that are associated with
Microsoft Virtual Server hosts, you must complete extra steps to account for
volumes in these environments.

A volume is a discrete unit of storage on disk, tape or other data recording medium
that supports some form of identifier and parameter list, such as a volume label or
input/output control.

Notes:
1. A volume should be mounted at only one mount point on the source host. A
volume mounted at multiple mount points is not supported.

680 IBMSystems Director Systems Management Guide

2. Make sure that the volume that contains the virtual server to be relocated does
not contain any files that are not related to the virtual server. If the volume
contains any files that are not related to the virtual server, everything in the
volume will become inaccessible as soon as the volume is dismounted.
3. When relocating multiple virtual servers on one volume, the relocation
operation succeeds only when all virtual servers on the same volume are
successfully relocated. The operation fails when any of the virtual servers on
the same volume fail to be relocated. In that case, all virtual servers on the
volume are registered again to the source host.
4. Relocation is supported on primary partitions only.

Complete the following steps to perform static relocation for virtual servers that
are associated with Microsoft Virtual Server hosts:
1. Create a volume on the storage area network (SAN). Make sure that the
volume you create is large enough to hold the virtual server.
2. Mount the volume at the source host.
3. Make sure that the destination host can access the volume as initialized or
formatted. If not, the destination host may need to be restarted. However, do
not mount the volume at the destination host.
4. Create a virtual server on the source host and put it on this volume.
5. Create relocation tasks for the virtual server.

Enabling secure copy (scp) for static relocation with

Virtualization manager subagent for ESX
If you want to use static relocation for VMware ESX Server hosts, you must enable
secure copy (scp) on all VMware ESX Server hosts.

Note: Secure copy is not required on hosts running VMware ESX Server 3.0
Service Console.

Secure copy must be enabled using RSA certificates, which provides secure transfer
of files without requiring the user ID and password for each file transfer operation.

Static relocation will fail for a destination host unless you can copy (or pull) a file
at the destination host from a source host by using the scp command without
entering a password.

If the hosts are moved to a different network, the steps in this procedure must be
repeated.

Complete the following steps to enable secure copy (scp) on a destination host that
is running Virtualization manager subagent for ESX:
1. Create an RSA public key.
a. At the command prompt of the source host, enter ssh-keygen -t rsa.
b. Store the generated key in a default location and do not use a passphrase.

Note: If you specify a different location other than /root/.ssh/, you must
adjust any other steps that use the default path.
2. Add the public key to the authorized_keys file for any ESX host that you want
to use as a destination host for relocation.
a. On the source host on which you created the RSA public key, copy the .pub
file to a directory that is accessible through File Transfer Protocol (FTP).

Chapter 14. Managing virtual environments 681

 b. Use FTP to log in to both ESX hosts (source and destination) and copy the
.pub file from the source host to the destination host.
c. From the console of the destination host, copy the .pub file to
/root/.ssh/authorized_keys.

Note: If this file already exists, do not overwrite it. Instead, add the
information in the .pub file to the existing /root/.ssh/authorized_keys file.
3. Change the permissions on the authorized_keys file and the ssh subdirectory.
a. On the console of the destination host, type cd /root.
b. Type chmod go-w .ssh .ssh/authorized_keys
4. On all ESX hosts that will be destination hosts, add the ESX host to the
known_host list.
a. On the console of the destination host, type ssh source_IPaddress.
b. b. When you are asked whether you want to add the host to the
known_host list, answer yes.
c. Exit from the secure shell.
d. Repeat steps a - c for all destination hosts until they have added the source
hosts to the known_host list.
e. Repeat steps a - c for all source hosts until each has added the destination
hosts to the known_host list.
5. Copy the required Perl scripts onto each host.
a. From the Comprehensive Perl Archive Network (CPAN), download the
ShellQuote.pm, SCP.pm, and SSH.pm scripts.
b. Copy SCP.pm and SSH.pm into /usr/lib/vmware/perl5/site_perl/
perl_version/Net/ directory, where perl_version is the version of Perl that you
are using. You might need to create the Net subdirectory.
c. Copy the ShellQuote.pm file into /usr/lib/vmware/perl5/site_perl/
perl_version/String/ Directory, where perl_version is the version of Perl that
you are using. You might need to create the String folder.

Relocating a virtual server

To optimize resource utilization, you can relocate a single virtual server from one
host to another. When the hosts are within the same virtual farm, you can relocate
all virtual servers on a host to another host.

Ensure that you meet the following requirements to relocate virtual servers:
v Relocation of virtual servers is only possible between hosts within the same
virtual farm.
v Both the source and target host must have access to a shared storage area
network (SAN).

Note: For Xen relocation, the virtual server image must be available on a shared
storage volume, with that volume mounted by both the source and target host.
v Both the source and target host must have access to a shared communications
network
v The target host must have enough memory to support the virtual server.

Note: Additionally, for Xen, the source host must have memory available that is
equal to or greater than the virtual server or virtual servers that you want to
relocate.
v The target host must support the configuration version of the virtual server.

682 IBMSystems Director Systems Management Guide

v Relocation of clustered virtual servers is not supported.
v Relocation of virtual servers that are suspended or in a transition state is not
supported.

Note: Additionally, for Xen, the virtual server cannot be in an offline or paused
state.
v Source and target hosts must have a virtual network device with the same label.

Note: For Xen, the bridge must have the same name on both the source and
target hosts.
v Virtual servers to be relocated cannot be connected to a removable device such
as a CD drive or diskette drive
v The version of a configuration file for a virtual server must be supported by the
virtualization application that Virtualization manager subagent communicates
with. Otherwise, the virtual server cannot be relocated.
v IBM® Power Systems only: To relocate a virtual server, ensure that you meet the
minimum virtualization software requirements.
Power Systems relocation leverages Live Partition Mobility functionality, a
component of the PowerVM Enterprise Edition hardware feature. To utilize the
relocation functionality in IBM Systems Director, you must meet the
requirements described in the “Live Partition Mobility” documentation. For
more information, see the preparation sections in the “Moving the mobile
partition using the HMC” or “Moving the mobile partition using the Integrated
Virtualization Manager” topics.

For further information about virtual server relocation for a specific virtualization
application, see its included documentation.

You can relocate a single virtual server or all virtual servers on a host by running
the relocation wizard. You can also create a relocation plan to facilitate relocation.
You can run the relocation plan immediately or save the plan to run later. The
Relocate Virtual Server wizard gives you the following options:
v Relocate and save plan
v Save plan only
v Relocate only

Note: With the Relocate only option, the relocation job is run directly.

To relocate one or more virtual servers using the Relocate Virtual Server wizard,
complete the following steps:
1. From the IBM Systems Director Server navigation area, expand Availability,
and click Relocate.
2. Complete the instructions in the relocation wizard.

To create a relocation plan, complete the following steps:

1. From the IBM Systems Director Server navigation area, expand Availability.
2. Click Relocation Plans.
3. On the Relocation Plans page, click Create in the menu bar.
4. Follow the instructions in the Create Relocation Plan wizard to create a
relocation plan.

Chapter 14. Managing virtual environments 683

 Related concepts
“Relocation requirements” on page 648
Live Partition Mobility
Related tasks
“Creating a virtual farm” on page 652
Moving the mobile partition using the HMC
Moving the mobile partition using the Integrated Virtualization Manager

Activating a relocation plan

After you have created and saved a relocation plan, you can run the relocation
plan, or schedule it to run at the appropriate time.

To run a relocation plan or schedule a relocation plan to run, complete the

following steps:
1. From the IBM Systems Director Server navigation area, expand Availability.
2. Click Relocation Plans to display all saved relocation plans.
3. Click the relocation plan you want to run or schedule to run.

Note: Ensure the relocation plan is accurate for the current environment. If
resources that are defined in the relocation plan have changed, or the plan has
been activated previously, it might not be valid.
4. In the scheduler window, the Run Now option is selected by default. Click OK
to run the relocation plan immediately, or select Schedule to specify the day
and time you want to schedule the relocation plan to run.
Related tasks
“Viewing relocation plans” on page 685

Deleting a relocation plan

If you no longer require a certain relocation plan, you can remove it from the
Relocation Plans view by deleting it.

To delete a relocation plan, complete the following steps:

1. From the IBM Systems Director Server navigation area, expand Availability.
2. Click Relocation Plans to display all saved relocation plans.
3. Select the relocation plan you want to delete and click Delete in the menu bar.
Related tasks
“Viewing relocation plans” on page 685

Editing a relocation plan

When you have defined a relocation plan, you can modify the plan by changing
the source host, target host, and other attributes of the plan with the Edit
Relocation Plan task.

To edit a relocation plan, complete the following steps:

1. From the IBM Systems Director Server navigation area, expand Availability.
2. Click Relocation Plans to display all saved relocation plans.
3. Select the relocation plan you want to change, and click Edit in the menu bar.
4. Follow the instructions in the wizard to edit the relocation plan.

684 IBMSystems Director Systems Management Guide

 Related tasks
“Viewing relocation plans”

Viewing relocation plans

You can access all of your saved relocation plans in one location by using the
relocation plan view.

From the relocation plan view, you can see all of your saved virtual-server
relocation plans, along with basic information about them: the type of relocation
plan (whether it is for a single virtual server, or for all virtual servers on the host),
the source host or virtual server, the target host, and a description of the plan. The
relocation plan view is also a single point of management from which you can
access tasks to edit, delete, or run existing relocation plans, or create new ones. You
can use this view to make any necessary changes to relocation plans to ensure that
they are accurate for the current environment, based on relocation plans being
activated or resources that are defined in the plan being changed.

To access the relocation plan view, complete the following steps:

1. From the IBM Systems Director navigation area, expand Availability.
2. Click Relocation Plans.
Related tasks
“Activating a relocation plan” on page 684
“Deleting a relocation plan” on page 684
“Editing a relocation plan” on page 684

Launch VMware ESX Manager User Interface

You can launch the VMware ESX Manager User Interface to manage your VMware
ESX hosts.

To launch the VMware ESX Manager User Interface, complete the following steps:
1. In the IBM Systems Director navigation pane, click Navigate Resources to
locate the host from which you want to start the VMware ESX Manager User
Interface.
2. Select the host, click Actions from the menu bar, and select System
Configuration → Launch VMware ESX Manager User Interface.
The VMware ESX Manager User Interface is started in a new window.

Launch VMware VirtualCenter Console

You can launch the VMware VirtualCenter Console to manage your VMware
VirtualCenter hosts.

To launch the VMware VirtualCenter Console, complete the following steps:

1. In the IBM Systems Director navigation pane, click Navigate Resources to
locate the host from which you want to start the VMware VirtualCenter
Console.
2. Select the host, click Actions from the menu bar, and select System
Configuration → Launch VMware VirtualCenter Console.
The VMware VirtualCenter Console is started in a new window.

Chapter 14. Managing virtual environments 685

 Launch VMware Infrastructure Client
You can launch the VMware Infrastructure Client to manage your VMware ESX
and VMware VirtualCenter hosts.

To launch the VMware Infrastructure Client, complete the following steps:

1. In the IBM Systems Director navigation pane, click Navigate Resources to
locate the host from which you want to start the VMware Infrastructure Client.
2. Select the host, click Actions from the menu bar, and select System
Configuration → Launch VMware Infrastructure Client.
The VMware Infrastructure Client is started in a new window.

Launch Microsoft Virtual Server Console

You can launch the Microsoft Virtual Server Console to manage your Microsoft
Virtual Server hosts.

To launch the Microsoft Virtual Server Console, complete the following steps:
1. In the IBM Systems Director navigation pane, click Navigate Resources to
locate the host from which you want to start the Microsoft Virtual Server
Console.
2. Select the host, click Actions from the menu bar, and select System
Configuration → Launch Microsoft Virtual Server Console.
The Microsoft Virtual Server Console is started in a new window.

686 IBMSystems Director Systems Management Guide

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 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

© Copyright IBM Corp. 1999, 2009 687

 Access Protocol (LDAP) 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 reference
Security requirements

Authenticating users to IBM Systems Director

Authentication is the process that IBM Systems Director uses to determine if the
identity claimed by an end 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.
Related tasks
Planning IBM Systems Director users and groups
Related reference
Security requirements

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 reference
Security requirements

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

688 IBMSystems Director Systems Management Guide

operating system, Lightweight Directory Access Protocol (LDAP), or the domain
controller. IBM Systems Director uses the user and group information for the
purpose of 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. 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.

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 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.
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.
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.

Chapter 15. Security 689

 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 cli 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 tasks
Planning IBM Systems Director users and groups

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.
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 users are authenticated to IBM Systems Director, you can configure the
authorizations for each user to IBM Systems Director tasks and resources.
Related concepts
“User authentication” on page 688
“Users and user groups in IBM Systems Director” on page 688

Authenticating IBM Systems Director users stored in the

domain server
IBM Systems Director can authenticate user login requests to a domain server.

To create a domain server user account that has access to IBM Systems Director
Server, complete the following steps:
1. Copy the product_install\lwi\conf\security.properties file to the
product_install\lwi\conf\override directory.
2. Update product_install\lwi\conf\override\security.properties to instruct
IBM Systems Director to use the domain server registry instead of the local
operating system registry.
3. Restart IBM Systems Director.

690 IBMSystems Director Systems Management Guide

 4. Create a user account in the domain server user registry. For instructions about
creating a user account in the domain server user registry, see your domain
server documentation.
5. 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.
6. 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 users are authenticated to IBM Systems Director, you can configure the
authorizations for each user to IBM Systems Director tasks and resources.
Related concepts
“User authentication” on page 688
“Users and user groups in IBM Systems Director” on page 688

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 particularly useful when you have a large number of
users who will operate IBM Systems Director. For IBM Systems Director user
authentication, LDAP has a number of advantages:
v Many companies already have existing LDAP directories of employees that can
be used for IBM Systems Director user authentication. These existing directories
save the time and effort required to create new user accounts on the
management server.
v An administrator can immediately modify or terminate a user’s access on all
instances of IBM Systems Director Server by changing the user’s LDAP group
memberships or by removing the user’s LDAP entry.
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,
complete the following steps:
1. Create a user account in the LDAP user registry. For instructions about creating
a user account in the LDAP user registry, see the documentation for your
LDAP server.
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
3. 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.

Chapter 15. Security 691

 4. Rename the <director_install>/lwi/conf/overrides/security.ldap template
properties file to <director_install>/lwi/conf/overrides/
securityLDAP.properties, where <director_install> is the IBM Systems
Director installation directory.
5. Open the securityLDAP.properties file in an editor and complete the following
edits:
v Modify the contents of this file to include the appropriate LDAP
configuration properties.
v Remove the security.properties file and any other security-related .properties
files.

Note: To encrypt the password field in securityLDAP.properties, change to the

<director_install>/lwi/bin directory and issue the following command:
lwiencoder -filename <director_install>/lwi/conf/overrides/securityLDAP.properties
-keylist com.ibm.lwi.LDAPAdminPassword
6. 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.
7. Restart IBM Systems Director.

After users are authenticated to IBM Systems Director, you can configure the
authorizations for each user to IBM Systems Director tasks and resources.
Related concepts
“User authentication” on page 688
“Users and user groups in IBM Systems Director” on page 688

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. 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.

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 desired.
6. Click OK.

692 IBMSystems Director Systems Management Guide

 Related concepts
“User authentication” on page 688
“Users and user groups in IBM Systems Director” on page 688

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 tasks
Integrating external applications into IBM Systems Director
Related reference
Security requirements

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.

Chapter 15. Security 693

 Related concepts
“Users and user groups in IBM Systems Director” on page 688
“Roles”
“Mappings” on page 712
Related reference
Security requirements

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 previous

versions of IBM Systems Director. 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 adds reusable roles that you can assign more than once
and use to build other roles. IBM Systems Director 6.1 also provides instance-based
authorization which 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.

694 IBMSystems Director Systems Management Guide

 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.
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
discovery manager, status manager, configuration 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
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.

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.

Chapter 15. Security 695

 Note: A user ID must have the AllPermission permission to run supported IBM
Director V5.20 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
Command Required permission Predefined role
chgp GeneralPermission SMManager
lsgp GeneralPermission SMUser
mkgp GeneralPermission SMManager
rmgp GeneralPermission SMManager

Discovery and inventory commands

Command Required permission Predefined role
collectinv InventoryPermission SMAdministrator
discover InventoryPermission SMAdministrator
lsinv InventoryPermission SMMonitor

Configuration plan and template commands

Command Required permission Predefined role
lscfgplan SystemConfigurationPermission SMMonitor
lscfgtmpl SystemConfigurationPermission SMMonitor
mkcfgplan SystemConfigurationPermission SMManager
mkcfgtmpl SystemConfigurationPermission SMManager
rmcfgplan SystemConfigurationPermission SMManager
rmcfgtmpl SystemConfigurationPermission SMManager

Status commands
Command Required permission Predefined role
chled SystemStatusAndHealthPermission SMManager
lsled SystemStatusAndHealthPermission SMMonitor
lsstatus SystemStatusAndHealthPermission SMMonitor

696 IBMSystems Director Systems Management Guide

Resource monitor commands
Command Required permission Predefined role
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

Command Required permission Predefined role
lsps SystemStatusAndHealthPermission SMMonitor
mkpmtask SystemStatusAndHealthPermission SMManager
rmpmtask SystemStatusAndHealthPermission SMManager

Event automation plan and event commands

Command Required permission Predefined role
chevtautopln AutomationPermission SMManager
evtacthist AutomationPermission SMManager
evtautopln AutomationPermission SMManager
evtlog AutomationPermission SMManager
lsevtact AutomationPermission SMMonitor
lsevtacthist AutomationPermission SMMonitor
lsevtautopln AutomationPermission SMMonitor
lsevtfltr AutomationPermission SMMonitor
lsevtlog AutomationPermission SMMonitor
lsevttype AutomationPermission SMMonitor
mkevtactemail AutomationPermission SMManager
mkevtactstpgm AutomationPermission SMManager
mkevtactsttask AutomationPermission SMManager
mkevtautopln AutomationPermission SMManager
rmevtact AutomationPermission SMManager
rmevtautopln AutomationPermission SMManager
rmevtfltr AutomationPermission SMManager
rmevtlog AutomationPermission SMManager

Chapter 15. Security 697

 Command Required permission Predefined role
testevtact AutomationPermission SMManager

Task and scheduled job commands

Command Required permission Predefined role
lsjob TaskManagementPermission SMUser
lsjobhistory TaskManagementPermission SMUser
lstask TaskManagementPermission SMUser
rmjob TaskManagementPermission SMAdministrator
rmjobhistory TaskManagementPermission SMAdministrator
runjob TaskManagementPermission SMUser
runtask TaskManagementPermission SMUser

Update commands
Command Required permission Predefined role
checkupd ReleaseManagementPermission SMMonitor
cleanupd ReleaseManagementPermission SMManager
importupd ReleaseManagementPermission SMManager
installupd ReleaseManagementPermission SMManager
lsupd ReleaseManagementPermission SMMonitor
uninstallupd ReleaseManagementPermission SMManager

Security commands
Command Required permission Predefined role
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
Command Required permission Predefined role
get SystemStatusAndHealthPermission SMMonitor
getbulk SystemStatusAndHealthPermission SMMonitor

698 IBMSystems Director Systems Management Guide

 Command Required permission Predefined role
getnext SystemStatusAndHealthPermission SMMonitor
inform SystemStatusAndHealthPermission SMManager
set SystemStatusAndHealthPermission SMManager
trap SystemStatusAndHealthPermission SMManager
walk SystemStatusAndHealthPermission SMMonitor

Storage commands
Command Required permission Predefined role
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
Command Required permission Predefined role
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:

Chapter 15. Security 699

 1. If the user account that is needed does not already 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 new 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 user groups in IBM Systems Director” on page 688
“User authorization” on page 693
“Roles” on page 694
Related tasks
“Assigning a role to a user or user group”
“Logging into IBM Systems Director Server” on page 75

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.

To assign a role to a 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 to which you want to assign a role.
3. Click Assign Role. The Assign Role Wizard Welcome page 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: The user will have access to all the resources contained in the selected
groups, even if any resources are also contained in other groups that are not
selected.
8. Click Next. The Summary page is displayed.
9. Click Finish.

700 IBMSystems Director Systems Management Guide

 Related concepts
“Users and user groups in IBM Systems Director” on page 688
“User authorization” on page 693
“Roles” on page 694
Related tasks
“Authorizing users to manage resources” on page 699

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:

1. In the IBM Systems Director Web interface navigation area, expand Security
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” on page 694
“Users and user groups in IBM Systems Director” on page 688
“User authorization” on page 693

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.

Chapter 15. Security 701

 To create a role, complete the following steps:
1. In the IBM Systems Director Web interface navigation area, expand Security
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. 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.
9. Click Next. The Summary Page is displayed.
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” on page 694
“Users and user groups in IBM Systems Director” on page 688
“User authorization” on page 693
Related tasks
“Managing roles”

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:

1. In the IBM Systems Director Web interface navigation area, expand Security
and click Roles.

702 IBMSystems Director Systems Management Guide

2. On the Roles page, select one of the following actions.
Table 47. Role actions
To do this task:
View details about an existing role
Copy an existing role
Edit an existing role
Delete an existing role
Complete these steps:
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.
Note: 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.
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.
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,
clicking Next to continue through the
wizard.
4. Click Finish.
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.
Chapter 15. Security 703
 Related concepts
“Roles” on page 694
“Users and user groups in IBM Systems Director” on page 688
“User authorization” on page 693
Related tasks
“Creating a role” on page 701

Managing credentials in IBM Systems Director

To enable single sign-on (SSO), IBM Systems Director supports mechanisms to
manage various forms of credentials using the credential transformation service (CTS).
Related tasks
“Viewing the discovery manager summary” on page 233
Related reference
Security requirements

Credentials
IBM Systems Director uses credentials and the credential transformation service (CTS)
to implement single sign-on authentication.

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, IBM Systems Director
provides a credential transformation service (CTS). A user’s credentials that access a
system are mapped to the appropriate credentials that the user needs for
authenticating to that system. With this service, IBM Systems Director users who
are managing remote systems over various security domains or realms can
authenticate and manage these remote systems by using credentials that are saved
in the registries.

When credentials are configured in IBM Systems Director, users are not required to
type the user ID and password for the target system each time that they or a task
access it. IBM Systems Director Server automatically logs in to the target system as
needed.

You can view information about your credential mappings on the IBM Systems
Director Web interface Welcome page.

With IBM Systems Director, you can manage shared, targeted, and access point
credentials.
Shared credentials
Shared credentials are those credentials that exist in an authentication
registry that is not specific to an access point. They must be of type user
ID/password. 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 Security → Credentials page
to manage shared credentials.
Targeted credentials
Targeted credentials are each assigned to only one access point and are
located in an authentication registry that is specific to that access point. In

704 IBMSystems Director Systems Management Guide

 IBM Systems Director, use Navigate Resources → All systems → (right-click
a system) → Security → Configure Access to manage targeted credentials.
Access point credentials
An access point is a logical address that a system uses to route data
between a remote device and the appropriate communications support.
Access point credentials incorporate both source and targeted credentials as
well as mappings between the credentials. In IBM Systems Director, use
Navigate Resources → All systems → (right-click a system) → Security →
Configure Access to manage access point credentials.
Related reference
Security requirements

Managing shared credentials

Use IBM Systems Director to configure the shared credentials that are used to log
in to and access systems that are managed by IBM Systems Director.

Shared credentials are those credentials that exist in an authentication registry that
is not specific to an access point. They must be of type user ID/password. 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 Security → Credentials page to manage shared credentials.

Creating shared credentials

Use the Credentials page to create shared credentials.

With IBM Systems Director, you can create shared credentials that can be used
across systems.

To create a set of shared user ID / password credentials, complete the following

steps:
1. In the IBM Systems Director Web interface navigation area, expand Security
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.

Chapter 15. Security 705

 6. Enter the appropriate login credentials for the system.
7. Click Next. The Summary page is displayed.
8. Click Finish.
Related concepts
“Credentials” on page 704
Related tasks
“Accessing a secured system with configure access” on page 715

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:
1. In the IBM Systems Director Web interface navigation area, expand Security
and click Credentials.
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.
6. Click Next. The Summary page is displayed.
7. Click Finish.
Related concepts
“Credentials” on page 704

Deleting shared credentials

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 tasks, and the task will no longer be able to access the system.

To delete a set of shared credentials, complete the following steps:

1. In the IBM Systems Director Web interface navigation area, expand Security
and click Credentials.
2. On the Credentials page, select the credentials that you want to delete.
3. Click Delete. A confirmation message is displayed.
4. Click OK.

706 IBMSystems Director Systems Management Guide

 Related concepts
“Credentials” on page 704

Managing targeted credentials

Use IBM Systems Director to configure the targeted credentials that are used to log
in to and access remote access points that are managed by IBM Systems Director.

Targeted credentials are each assigned to only one access point and are located in
an authentication registry that is specific to that access point. In IBM Systems
Director, use Navigate Resources → All systems → (right-click a system) → Security
→ Configure Access to manage targeted 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: If any CAS or IPC access points exist on the resource, you cannot use this
process to configure credentials for any of the agent access points, which are all
access points that have an access type other than console. (You can still use this
process to configure credentials for console access points.) When the agent access
points include CAS or IPC access points, using the request access task to
successfully request access to the resource is all that is required to obtain access to
all the agent access points. Credentials and mappings are created for the agent
access points, but you cannot view or manage them.

To create a set of targeted credentials, complete the following steps:

1. In the IBM Systems Director Web interface navigation area, click Navigate
Resources → group name → system name.
2. Click Actions → Security → Configure Access. The Configure Access page is
displayed.
3. Click an access point with an access type other than console. 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.

Chapter 15. Security 707

 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
a new 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. Fill in the values for the chosen credential type.
9. Click Next. The Summary page is displayed.
10. Click Finish.
Related concepts
“Credentials” on page 704
Related tasks
“Accessing a secured system with configure access” on page 715

Editing targeted credentials

Use the Edit Credential Wizard to edit targeted credentials.

To edit a targeted credential, complete the following steps:

1. In the IBM Systems Director Web interface navigation area, click Navigate
Resources → group name → system name.
2. Click Actions → Security → Configure Access. The Configure Access page is
displayed.
3. Click an access point with an access type other than console. The credentials
associated with that access point are listed.
4. Select the credential that you want to edit.
5. Click Edit. The Edit Credential Wizard is displayed.
6. Change the details that are available for changing.
7. Click Next. The Summary page is displayed.
8. Click Finish.
Related concepts
“Credentials” on page 704

Deleting targeted credentials

Use the Configure Credential Wizard to delete targeted 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.

708 IBMSystems Director Systems Management Guide

 Note: You will not receive a warning when deleting a credential that is associated
with an automated tasks, and the task will no longer be able to access the system.

To delete a set of targeted credentials, complete the following steps:

1. In the IBM Systems Director Web interface navigation area, click Navigate
Resources → group name → system name.
2. Click Actions → Security → Configure Access. The Configure Access page is
displayed.
3. On the Configure Access page, select the credentials that you want to delete.
4. Click Delete. A confirmation message is displayed.
5. Click OK.
Related concepts
“Credentials” on page 704

Managing console access point credentials

Use IBM Systems Director to create a source or target credential and map the
credential on one machine to another credential on another machine.

An access point is a logical address that a system uses to route data between a
remote device and the appropriate communications support. Access point
credentials incorporate both source and targeted credentials as well as mappings
between the credentials. In IBM Systems Director, use Navigate Resources → All
systems → (right-click a system) → Security → Configure Access to manage access
point credentials.

Creating console access point credentials

Use the Configure Credential Wizard to create access point credentials.

Creating an access point credential involves choosing a target credential and then
mapping it to a source credential.

To create a set of access point credentials, complete the following steps:

1. In the IBM Systems Director Web interface navigation area, click Navigate
Resources → group name → system name.
2. Click Actions → Security → Configure Access. The Configure Access page is
displayed.
3. Click an access point with an access type of console. 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 Details page is
displayed.
6. 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.

Chapter 15. Security 709

 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.
7. Enter the appropriate login credentials for the system.
8. Click Next. The Source Credential page is displayed.
9. Select the source credential that you want to use. You can use either the
current console credential or choose another credential from the table.
10. Click Next. The Summary page is displayed.
11. Click Finish.
Related concepts
“Credentials” on page 704
Related tasks
“Accessing a secured system with configure access” on page 715

Editing console access point credentials

Use the Edit Credential Wizard to edit access point credentials.

To edit an access point credential, complete the following steps:

1. In the IBM Systems Director Web interface navigation area, click Navigate
Resources → group name → system name.
2. Click Actions → Security → Configure Access. The Configure Access page is
displayed.
3. Click an access point with an access type other than console. The credentials
associated with that access point are listed.
4. Select the credential that you want to edit.
5. Click Edit. The Edit Credential Wizard is displayed.
6. Change the details that are available for changing.
7. Click Next. The Summary page is displayed.
8. Click Finish.
Related concepts
“Credentials” on page 704

Deleting console access point credentials

Use the Configure Credential Wizard to delete access point 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 tasks, and the task will no longer be able to access the system.

To delete a set of access point credentials, complete the following steps:

1. In the IBM Systems Director Web interface navigation area, click Navigate
Resources → group name → system name.

710 IBMSystems Director Systems Management Guide

 2. Click Actions → Security → Configure Access. The Configure Access page is
displayed.
3. On the Configure Access page, select the credentials that you want to delete.
4. Click Delete. A confirmation message is displayed.
5. Click OK.
Related concepts
“Credentials” on page 704

Configuring the authentication registry

Use the Configure Authentication Registry Wizard to configure IBM Systems
Director with the authentication registry that the selected console-type access point
uses to authenticate credentials on the remote system.

To configure the authentication registry, complete the following steps:

1. In the IBM Systems Director Web interface navigation area, click Navigate
Resources → group name → system name.
2. Click Actions → Security → Configure Access. The Configure Access page is
displayed.
3. Click an access point with an access type of console. The credentials currently
configured for that access point are listed.
4. Click Configure Authentication Registry. The Configure Authentication
Registry Wizard is displayed.
5. If the Welcome page is displayed, click Next. The Authentication Registry
Type page is displayed.
6. From the Authentication Registry Type list, select the type of authentication
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
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.
7. If you chose LDAP or Domain and previously used the credentials or
configure access tasks to identify LDAP or domain authentication registries,
select the one you want to use from the list.
8. If you chose LDAP or Domain, enter the IP address or host name of the
specific LDAP server or domain.
9. Click Next. The Summary page is displayed.
10. Click Finish.

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.

Chapter 15. Security 711

 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 administrative overhead of
creating 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, CTS requires
that this type of mapping associate 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:
1. In the IBM Systems Director Web interface navigation area, expand Security
and click Credentials.
2. On the Credentials page, select the credential that you want to map.
3. Click Actions → Mapping.
4. On the Mapping page, click Create. The Mapping Wizard opens.
5. If the Welcome page is displayed, click Next. The Target credential page is
displayed and contains information about the selected credential.
6. Click Next. The Source credential page is displayed.
7. 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.
8. Click Next. The Summary page is displayed.

712 IBMSystems Director Systems Management Guide

 9. Click Finish.
Related concepts
“Mappings” on page 712

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:

1. In the IBM Systems Director Web interface navigation area, expand Security
and click Credentials.
2. On the Credentials page, select the credential that you want to edit.
3. Click Actions → Mapping.
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 Target credential page is
displayed and contains information about the selected credential.
7. Click Next. The Source credential page is displayed.
8. Select if you would like to use the current console credential or a credential
that was previously created and is displayed in the credential table.
9. If you choose to select a credential from the table, select it.
10. Click Next. The Summary page is displayed.
11. Click Finish.
Related concepts
“Mappings” on page 712

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:

1. In the IBM Systems Director Web interface navigation area, expand Security
and click Credentials.
2. On the Credentials page, select the credential that contains the mapping that
you want to delete.
3. Click Actions → Mapping.
4. On the Mapping page, select the mapping that you want to delete.
5. Click Delete. A confirmation message is displayed.
6. Click Ok.
Related concepts
“Mappings” on page 712

Managing access
Use IBM Systems Director to request access to, revoke access from, and configure
access options for systems in your environment.

You can request access to resources using either the request access task or the
configure access task. You can also revoke access to an accessed system.

Chapter 15. Security 713

 Related concepts
“Discovery” on page 231
“Discovery protocols” on page 232
“System discovery” on page 237
“Discovery profiles” on page 239
Related tasks
“Creating a discovery profile” on page 34

Accessing a secured system with request access

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.

Ensure that you have the correct authorization to access the secured system.

Note: If any CAS or IPC access points exist on the resource, you must use this
process to configure credentials for all of the agent access points, which are all
access points that have an access type other than console. When the agent access
points include CAS or IPC access points, using the request access task to
successfully request access to the resource is all that is required to obtain access to
all the agent access points. Credentials and mappings are created for the agent
access points, but you cannot view or manage them. If no CAS or IPC access
points exist on the resource, you have the option of using the configure access task
to request access to the secured resource.

Secured systems are displayed in IBM Systems Director Web interface with a
padlock icon beside them in the Secured 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 resources that have an access status of Offline, for which you need
to instead use verify access, or OK, because you already have access to those
resources and no further action is required.

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 Navigate Resources.
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 with
administrator privileges on the managed system.
5. Click Request Access. Credentials are created and authenticated to the
managed system in an attempt to access it.

714 IBMSystems Director Systems Management Guide

 If the access request is successful, the access status for the managed system will
change to OK.
Related concepts
The Start page
“Discovery” on page 231
“Discovery protocols” on page 232
“System discovery” on page 237
Related tasks
“Viewing the discovery manager summary” on page 233
“Performing initial discovery” on page 235
“Performing a system discovery” on page 32
“Performing an advanced system discovery” on page 48
“Collecting and viewing inventory data” on page 259
“Accessing a secured system with configure access”

Accessing a secured system with configure access

Use the Apply Credentials feature on the Configure Access page to request access
to the remote access points of a resource.

Ensure that you have the correct authorization to access the resource and its access
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: If any CAS or IPC access points exist on the resource, you cannot use this
process to configure credentials for any of the agent access points, which are all
access points that have an access type other than console. (You can still use this
process to configure credentials for console access points.) When the agent access
points include CAS or IPC access points, using the request access task to
successfully request access to the resource is all that is required to obtain access to
all the agent access points. Credentials and mappings are created for the agent
access points, but you cannot view or manage them.

To configure access for secured managed systems, complete the following steps:
1. In IBM Systems Director Web interface click Navigate Resources.
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 desired type of credential.
6. Repeat the credential creation process for each access point that you plan to
use.
7. Select Apply Credentials to authenticate the credentials and request access to
all agent access points that are not already accessible.

Note: If you already have access to all agent access points, Apply Credentials
is disabled.

Chapter 15. Security 715

 If you are successful in obtaining access to all access points on a resource, its
access state will display OK.
Related tasks
“Viewing SNMP device attributes” on page 323
“Accessing a secured system with request access” on page 714
“Creating shared credentials” on page 705
“Creating targeted credentials” on page 707
“Creating console access point credentials” on page 709

Revoking access to a secured system

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, before you can revoke its access.

To revoke access to secured managed systems, complete the following steps.

Note: You can select more than one accessible system at a time.
1. In IBM Systems Director Web interface click Navigate Resources.
2. Navigate to the system to which you want to revoke access.
3. Right-click the system and select Security → Revoke Access.
4. Click OK.

If the access revocation is successful, the access status will change to No access.

Encrypting passwords for database configuration

Encrypt passwords for your database configuration before you run the cfgdbcmd
tool.

Complete the following steps for your operating system to encrypt passwords for
your database configuration:
v Encrypt passwords on Windows:

Note: You do not need to run cfgserver.bat -db if you previously configured
your database by running cfgserver.bat -all.
1. Open a command prompt.
2. Change your working directory to install_root\bin, where install_root is the
root directory of your IBM Systems Director installation.
3. Run cfgserver.bat -db.
4. Provide the information requested by the script, pressing Enter after every
answer. This script prompts for the user ID and password for the chosen
database server and writes the user ID and the encrypted password to the
response file in the DbmsUserId and DbmsPassword fields.

Note: If you have multiple database sections in the response file, this script
overwrites the user ID and password for each database section
v Encrypt passwords on AIX or Linux:
1. Run the install_root/bin/configDB.sh file, where install_root is the root
directory of your IBM Systems Director installation.

716 IBMSystems Director Systems Management Guide

 2. Provide the information requested by the script, pressing Enter after every
answer.

Note: If you are encrypting passwords for IBM DB2 Universal Database™,
you are asked for the IBM DB2 Universal Database credentials as well as the
tpm credentials. For the tpm credentials enter in the operating system
credentials used to access the IBM Systems Director Server.
Related tasks
Configuring the database application after IBM Systems Director installation
Preparing the database application

Chapter 15. Security 717

718 IBMSystems Director Systems Management Guide
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 Director topic collection in the IBM® Systems Information Center,
and its related publications, are accessibility-enabled. The accessibility features of
the information center are described at publib.boulder.ibm.com/infocenter/
director/v6r1x/topic/com.ibm.help.ic.doc_3.4.1/info_accessibility.html.

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.

Keyboard navigation

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+DownArrow. To then navigate in the
combination box, press the arrow keys.
v In the navigation pane, each node is a single list item. If using the JAWS screen
reader, press Insert+Tab to read the selected node.

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

© Copyright IBM Corp. 1999, 2009 719

 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.

Interface information

Restrictions:
v When using a screen reader such as JAWS, the Firefox Web browser is
recommended. Certain functions, such as dynamic refresh do not work correctly
when using Internet Explorer with JAWS screen reader. dynamic refresh
v In the Scheduler page, the Time entry field and calendar are not readable by the
JAWS screen reader.
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.

Turning off table features that are not accessible

IBM Systems Director Web interface supports basic accessibility tasks (for example,
adjusting display attributes such as color, contrast and font size) that are enabled
by your Web browser. Refer to your Web browser documentation for more
information about accessibility tasks.

You can turn off table features that are not accessible in the interface, such as fixed
column width. This option is not selected by default. To turn off table features that
are not accessible:
1. In the navigation area of the IBM Systems Director Web interface, expand
Settings and click Navigation Preferences.
2. Select Enable tables for accessibility, and then click OK.

720 IBMSystems Director Systems Management Guide

Playing a sound when data on the page changes

To play a sound when data on the page changes:

1. In the navigation area of the IBM Systems Director Web interface, expand
Settings and click Navigation Preferences.
2. Select Play sound when data on the page changes, and then click OK.

IBM and accessibility

See the IBM Human Ability and Accessibility Center for more information about
the commitment that IBM® has to accessibility.

Appendix. Accessibility 721

722 IBMSystems Director Systems Management Guide
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 (DBCS) information, contact the IBM®
Intellectual Property Department in your country or send inquiries, in writing, to:

IBM World Trade Asia Corporation

Licensing 2-31 Roppongi 3-chome, Minato-ku
Tokyo 106-0032, 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.

© Copyright IBM Corp. 1999, 2009 723

 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
MW9A/050
5600 Cottle Road
San Jose, CA 95193
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.

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.

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 Corporation in the United States, other countries,
or both. If these and other IBM® trademarked terms are marked on their first
occurrence in this information with a trademark symbol (® or ™), these symbols
indicate U.S. registered or common law trademarks owned by IBM® at the time
this information was published. Such trademarks may also be registered or

724 IBMSystems Director Systems Management Guide

common law trademarks in other countries. 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.

Intel is a trademark or registered trademark of Intel Corporation or its subsidiaries

in the United States and other countries.

Java and the Java logo are a trademark of Sun Microsystems, Inc. in the United
States, other countries, or both.

Linux is a registered trademark of Linus Torvalds in the United States, other

countries, or both.

Microsoft and Windows 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 725
726 IBMSystems Director Systems Management Guide
Glossary
This glossary includes terms and definitions for IBM Systems Director.
To view glossaries for other IBM products, go to
www.ibm.com/software/globalization/
terminology/.
A A system that does not have an agent
Advanced Encryption Standard (AES)
A data encryption technique that
improved upon and officially replaced the
Data Encryption Standard (DES). AES is
sometimes referred to as Rijndael, which
is the algorithm on which the standard is
based.
Advanced System Management interconnect
(ASM interconnect)
A feature of IBM service processors that
enables users to connect up to 24 servers
to one service processor, thus eliminating
the need for multiple modems,
telephones, and LAN ports. It provides
such out-of-band management functions
as system power control,
service-processor event-log management,
firmware updates, alert notification, and
user profile configuration.
Advanced System Management processor (ASM
processor)
A service processor built into the
mid-range Netfinity® and early xSeries
servers. IBM Director can connect
out-of-band to an ASM processor located
on an ASM interconnect; an ASM PCI
adapter, a Remote Supervisor Adapter, or
a Remote Supervisor II must serve as the
gateway service processor.
AES See Advanced Encryption Standard.
agentless
Pertaining 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 computer.
agent manager
A network service that provides
authentication and authorization and that
maintains a registry of configuration
© Copyright IBM Corp. 1999, 2009
information about the common agents
and resource managers in a user’s
environment.
Agentless-managed 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
operating system and hardware: discover
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
alert A message or other indication that signals
an event or an impending event.
alert forwarding
A function that ensures that alerts are
sent, even if a managed system
experiences a catastrophic failure, such as
an operating-system failure.
Alert Standard Format (ASF)
A protocol for the remote management of
systems in environments without
operating systems.
ASM interconnect
See Advanced System Management
interconnect.
ASM processor
See Advanced System Management
processor.
Auto-Logical Drive Transfer
See auto volume transfer/auto disk
transfer.
auto volume transfer/auto disk transfer
(AVT/ADT)
A function that provides automatic
failover in case of controller failure on a
storage subsystem.
727
AVT/ADT
See auto volume transfer/auto disk
transfer.
B detect-and-deploy profile also can include
Basic Input/Output System (BIOS)
The code that controls basic hardware
operations, such as interactions with
diskette drives, hard disk drives, and the
keyboard.
Bash shell
An sh-compatible shell that incorporates
the positive aspects of Korn shell and C
shell. It serves as the GNU operating
system’s command language interpreter.
BIOS See Basic Input/Output System.
Blade slot connection
The connection between the SAS
connectivity module and a BladeCenter
server blade.
Basic Zone Permission Table
A table on the Manage Fabric page. Use it
to map zone groups with hosts to zone
groups that have storage that you want
those hosts to have access to.
BladeCenter chassis
A BladeCenter unit that acts as an
enclosure. This 7-U modular chassis can
contain up to 14 blade servers. It enables
the individual blade servers to share
resources, such as the management,
switch, power, and blower modules.
blade server
A high-throughput, two-way, Intel
Xeon-based server on a card that supports
symmetric multiprocessors (SMPs).
browser system
A system that connects to the IBM
Systems Director Web interface on the
management server through a Web
browser.
C on the operating system and hardware.
chassis
The metal frame in which various
electronic components are mounted.
chassis detect-and-deploy profile
A profile that IBM Director automatically
applies to all new BladeCenter chassis
when they are discovered. The profile
settings include management module
728 IBMSystems Director Systems Management Guide
name, network protocols, and static IP
addresses. If Remote Deployment
Manager (RDM) is installed on the
management server, the chassis
deployment policies.
CIM See Common Information Model.
cloning
In z/VM, a copying technique that
preserves the characteristics of the
original but personalizes instance-specific
data. The result of a cloning operation is
new instance of an entity (for example, of
a virtual disk, a virtual computer system,
or an operating system) rather than a
backup of the original.
cluster
A collection of complete systems that
work together to provide a single, unified
computing capability.
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; additional event
support; monitor processes and resources,
and set critical thresholds that send
notifications when triggered; manage
operating system resources and processes.
Common Agent-managed system
An IBM or non-IBM server, desktop
computer, workstation, or mobile
computer that has Common Agent
installed. The function of a Common
Agent-managed system varies depending
Common Information Model (CIM)
An implementation-neutral,
object-oriented schema for describing
network management information. The
Distributed Management Task Force
(DMTF) develops and maintains CIM
specifications.
configuration plan
A set of configuration templates used to
configure a system.
configuration setting
Realtime definition of a system or device,
which can be saved as a configuration
template. You can save configuration
settings from a system and turn then into
configuration templates, or you can create
configuration setting 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
without having it as a member of a
configuration plan.
D are transmitted over a physical link, dword
database
The database that contains the data stored
by IBM Systems Director Server.
database server
The server on which the database
application and database are installed.
Data Encryption Standard (DES)
A cryptographic algorithm designed to
encrypt and decrypt data using a private
key.
DES See Data Encryption Standard.
Diffie-Hellman key exchange
A public, key-exchange algorithm that is
used for securely establishing a shared
secret over an insecure channel.
digital signature algorithm (DSA)
A security protocol that uses a pair of
keys (one public and one private) and a
one-way encryption algorithm to provide
a robust way of authenticating users and
systems. If a public key can successfully
decrypt a digital signature, a user can be
sure that the signature was encrypted
using the private key.
discovery
The process of finding resources within
an enterprise, including finding the new
location of monitored resources that were
moved.
disk pool
In z/VM Center, a logical grouping of
contiguous disk spaces. A disk pool can
include disk spaces from multiple
physical disks. A disk pool corresponds to
a z/VM Directory Maintenance Facility
allocation group.
distributed component object model (DCOM)
An extension of the Microsoft Component
Object Model (COM) to support objects
distributed across a network.
Domain
A group of IP addresses that corresponds
to a specific site, group, university,
company, or other organization.
DSA See digital signature algorithm.
Dword
A sequence of four contiguous bytes or
characters which, together, are considered
one unit. When discussing the bits that
represents four characters (or 40 bits).
When discussing the contents of a frame
after 10b8b decoding, dword represents
four bytes (or 32 bits).
Dword sync
Dword synchronization. Detection of an
incoming stream of dwords from a
physical link by a PHY.
E
ECM Expander connection manager. An object
within an expander that manages routing.
enclosure
A unit that houses the components of a
storage subsystem, such as a control unit,
disk drives, and power source.
endpoint
The system that is the origin or
destination of a session.
event An occurrence of significance to a task or
system. Events can include completion or
failure of an operation, a user action, or
the change in state of a process.
event action
The action that IBM Director takes in
response to a specific event or events.
event-automation plan
A user-defined plan that determines how
IBM Systems Director will manage certain
events. An event action plan comprises
one or more event filters and one or more
customized event actions.
Glossary 729
event filter
A filter that specifies the event criteria for
an event action plan. Events must meet
the criteria specified in the event filter in
order to be processed by the event action
plan to which the filter is assigned.
Expander
A device that enables quick aggregation
of several disk drives in a single SAS
domain. An expander can connect
multiple hosts to multiple targets. A SAS
connectivity module is an expander.
Extensible Markup Language (XML)
A standard metalanguage for defining
markup languages that is based on
Standard Generalized Markup Language
(SGML).
F
fabric A complex network using hubs, switches,
and gateways. Fibre channel uses a fabric
to connect devices.
field-replaceable unit (FRU)
An assembly that is replaced in its
entirety when any one of its components
fails.
File Transfer Protocol (FTP)
In TCP/IP, an application layer protocol
that uses TCP and Telnet services to
transfer bulk-data files between machines
or hosts.
FRU See field-replaceable unit.
G
gateway
gigabyte (GB)
In decimal notation, 1 073 741 824 when
referring to memory capacity; in all other
cases, it is defined as 1 000 000 000.
group A logical set of managed objects. Groups
can be dynamic, static, or task-based.
H
HBA Host bus adapter. It plugs into a host so
that it can communicate with a SCSI
device.
host object
A logical object that groups one or more
worldwide port names (WWPNs) of the
730 IBMSystems Director Systems Management Guide
host bus adapters (HBAs) that the cluster
has detected on the storage area network
(SAN).
host system
A system that contains resources from
which virtual servers are constructed.
HT See Hyper-Threading.
Hyper-Threading (HT)
A technology with which a single
processor can function as two virtual
processors and execute two threads
simultaneously.
hypervisor
A program or a portion of Licensed
Internal Code (LIC) that allows multiple
instances of operating systems to run
simultaneously on the same hardware.
I
IBM Systems Director environment
The complex, heterogeneous environment
managed by IBM Director. It includes
systems, BladeCenter chassis, software,
and SNMP devices.
IBM Systems Director plug-ins
A tool that extends the functionality of
IBM Systems Director (for example,
Electronic Service Agent).
IBM Systems Director Server
The main component of IBM Director
software. When installed on the
management server, it provides basic
functions such as discovery of the
managed systems, persistent storage of
configuration and management data, an
inventory database, event listening,
security and authentication, management
console support, and administrative tasks.
IBM Systems Director Server service
A service that runs automatically on the
management server, and provides the
server engine and application logic for
IBM Systems Director.
IBM Director service account
The Windows operating-system account
associated with the IBM Director Server
service.
image A bootable operating system and
additional software in the form of a single
raw image file. You can store, copy, and
 customize system images to reuse them
for creating virtual servers.
image repository
A part of a local or shared file system that
is used to store system images.
inband communication
Pertaining to events that are transmitted
between IBM Systems Director Server and
service processors in systems that are
running the required IBM Systems
Director agent
Initiator
A SCSI device that asks another SCSI
device (the target) to perform an
operation. Usually, a host computer acts
as an initiator and a peripheral device
acts as a target. With SAS zoning,
initiators and targets can see only parts of
a domain. These parts are called zone
groups.
instance
An individual realization of the operating
system with a particular version,
configuration, physical location, and
identifier.
In object-oriented programming, an object
of a particular class.
integrated system management processor
(ISMP)
A service processor built into some
xSeries servers. ISMP is the successor to
the Advanced System Management (ASM)
processor.
Intelligent Peripheral Management Interface
(IPMI)
A standard for controlling intelligent
devices that monitor a system. It provides
for dynamic discovery of sensors in the
system and the ability to monitor the
sensors and be informed when the
sensor’s values change or go outside
certain boundaries.
interprocess communication (IPC)
1. The process by which programs send
messages to each other. Sockets,
semaphores, signals, and internal
message queues are common methods
of interprocess communication.
2. A mechanism of an operating system
that allows processes to communicate
with each other within the same
computer or over a network.
IPC See interprocess communication.
ISMP See integrated system management
processor.
iso image
A disk image for an ISO 9660 file system,
containing the installable files for a
particular update or upgrade.
inventory data
Information about physical, logical, and
virtual hardware (such as virtual systems,
virtual servers, and farms), software
applications, operating systems,
middleware, firmware and BIOS,
diagnostics, and network.
J
job A separately runnable unit of work.
job instance
A specific occurrence of a job that is
running or has completed running.
K
keystore
In security, a storage object, either a file or
a hardware cryptographic card, where
identities and private keys are stored, for
authentication and encryption purposes.
Some keystores also contain trusted, or
public, keys.
L
launched task
Tasks that start outside of the IBM
Systems Director Web interface.
light path diagnostics
A technology that provides a lighted path
to failed or failing components to
expedite hardware repairs.
logical unit number (LUN)
In the Small Computer System Interface
(SCSI) standard, a unique identifier used
to differentiate devices, each of which is a
logical unit (LU).
Loss dword sync
An error that occurs when a PHY stops
detecting an incoming stream of dwords.
LUN See logical unit number.
Glossary 731
M nonvolatile random access memory (NVRAM)
MAC address
See Media Access Control address.
management module
The BladeCenter component that handles
system-management functions. It
configures the chassis and switch
modules, communicates with the blade
servers and all I/O modules, multiplexes
the keyboard/video/mouse (KVM), and
monitors critical information about the
chassis and blade servers.
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.
management server
The server on which IBM Director Server
is installed.
Media Access Control address (MAC address)
In a local area network, the protocol that
determines which device has access to the
transmission medium at a given time.
megabyte (MB)
For processor storage, real and virtual
storage, and channel volume, 2 to the
20th power or 1 048 576 bytes.
For disk storage capacity and
communications volume, 1 000 000 bytes.
N
network interface card
A printed circuit board that plugs into a
personal computer, server, or workstation.
It controls the exchange of data over a
network and provides the electronic
functions for the data-link protocol or
access method, such as token ring or
Ethernet.
network interface controller (NIC)
Hardware that provides the interface
control between system main storage and
external high-speed link (HSL) ports.
Network News Transfer Protocol (NNTP)
A protocol that is used to post messages
in, distribute messages to, and retrieve
messages from news groups and to
transfer articles between news servers.
732 IBMSystems Director Systems Management Guide
Random access memory (storage) that
retains its contents after the electrical
power to the machine is shut off.
NVRAM
See nonvolatile random access memory.
O
out-of-band communication
Pertaining to events that are 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.
P
PCI See Peripheral Component Interconnect.
See also Peripheral Component
Interconnect-X.
PCI-X See Peripheral Component Interconnect-X.
See also Peripheral Component
Interconnect.
Peripheral Component Interconnect (PCI)
A local bus that provides a high-speed
data path between the processor and
attached devices. See also Peripheral
Component Interconnect-X.
Peripheral Component Interconnect-X (PCI-X)
An enhancement to the Peripheral
Component Interconnect (PCI)
architecture. PCI-X enhances the
Peripheral Component Interconnect (PCI)
standard by doubling the throughput
capability and providing additional
adapter-performance options while
maintaining backward compatibility with
PCI adapters. See also Peripheral
Component Interconnect.
persistent
Pertaining to data that is maintained
across session boundaries, usually in
nonvolatile storage such as a database
system or a directory.
PFA See Predictive Failure Analysis.
PHY Physical layer. A PHY is responsible for
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 Director managed object that
decrypt. The private key is also used to
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
operating system and hardware: discover
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, 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 733
 resource. For example, a resource memory space and access to all associated
manager installs bundles on the agent adapters. A scalable partition is the logical
and starts and stops a subagent. equivalent of a physical platform. Scalable
partitions are associated with scalable
resource-monitor threshold
systems and comprise only the scalable
The point at which a resource monitor
nodes from their associated scalable
generates an event.
systems.
root user
scalable system
1. In Linux and UNIX operating An IBM Director managed object that
systems, a user who has superuser consists of scalable nodes and the scalable
authority and root privileges. A root partitions that are composed of the
user’s user identifier (UID) is 0. 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 Director managed object that
protocol for securely getting access to a
defines the scalable nodes that can run a
remote computer.
single image of the operating system. A
scalable partition has a single, continuous

734 IBMSystems Director Systems Management Guide

server farm system, this feature enables SNMP-based
A group of network servers that are managers to poll the managed system and
housed in one location. receive its alerts. If System Health
Monitoring is installed on the managed
Service delivery subsystem
system also, hardware alerts can be
A SAS domain.
forwarded as SNMP traps.
Service Location Protocol (SLP)
SNMP device
An Internet protocol that identifies and
An embedded device that uses SNMP to
uses network hosts without having to
monitor network-attached devices,
designate a specific network host name.
printers, or computers for conditions that
service processor require system-management attention.
A generic term for Remote Supervisor
SOAP See Simple Object Access Protocol.
Adapters, Advanced System Management
processors, Advanced System SQL See Structured Query Language.
Management PCI adapters, 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 Director to software.
provide hardware status and alert
static partition
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 Director Agent feature that database.
enables SNMP to access managed-system
data. When installed on a managed

Glossary 735
Subtractive routing attribute
The attribute of an expander PHY that
indicates that it can be used by the ECM
to route connection requests to an
attached expander device.
Subtractive routing method
The method the ECM uses to route
connection requests to an expander
device.
switch module
The BladeCenter component that provides
network connectivity for the BladeCenter
chassis and blade servers. It also provides
interconnectivity between the
management module and blade servers.
system
Operating-system-based or
hardware-based endpoint that has an IP
address and host name and can be
discovered and managed by IBM Systems
Director. For example, storage devices,
network devices, physical servers, virtual
servers, and operating systems are
systems.
system management BIOS (SMBIOS)
A specification that extends BIOS to
support the retrieval of management data.
system variable
A user-defined keyword and value pair
that can be used to test and track the
status of network resources. System
variables can be referred to wherever
event-data substitution is allowed.
T
Target Another SCSI device that communicates
with the originating SCSI device.
target system
A managed system on which an IBM
Systems Director task is performed.
terabyte (TB)
For processor storage, real and virtual
storage, and channel volume, 2 to the
40th power or 1 099 511 627 776 bytes.
For disk storage capacity and
communications volume, 1 000 000 000
000 bytes.
Topology
The geometric configuration of a
computer network, or how the network is
physically laid out. Common topologies
736 IBMSystems Director Systems Management Guide
are star (centralized), bus (decentralized),
and ring (decentralized).
triple Data Encryption Standard (triple DES)
A block cipher algorithm that can be used
to encrypt data transmitted between
managed systems and the management
server. Triple DES is a security
enhancement of DES that employs three
successive DES block operations.
triple DES
See triple Data Encryption Standard.
Trivial File Transfer Protocol (TFTP)
In Internet communications, a set of
conventions that transfers files between
hosts using minimal protocol.
trustore
In security, a storage object, either a file or
a hardware cryptographic card, where
public keys are stored in the form of
trusted certificates, for authentication
purposes in Web transactions. In some
applications, these trusted certificates are
moved into the application keystore to
reside with the private keys.
U
Universally Unique Identifier (UUID)
The 128-bit numerical identifier that is
used to ensure that two components do
not have the same identifier.
undoable disk
A type of virtual disk that saves changes
to a temporary file instead of to the
virtual disk itself. Changes can be
committed when the virtual machine is
powered off.
UUID See Universal Unique Identifier.
V
viewport
1. In the GDDM® function, a rectangular
area within the picture space that
defines where the output of the
current page appears on the work
station.
2. In GL, the last transformation in the
graphics pipeline, which is used to
map from normalized device
coordinates to device coordinates. The
viewport maps the unit cube x/w =
 +/-1, y/w = +/-1, z/w = +/-1 to the
screen space, as measured in pixels.
3. That portion of a partition or usable
area defined for display of data to the
operator. The viewport has a
predefined size and position on the
screen and is related to a presentation
space through a specified window.
4. In BMS, that part of a screen that is
allocated to a partition.
virtual farm
A collection of host systems and their
associated virtual servers. Virtual farms
can represent farms that are defined in
VMware VirtualCenter. Virtual farms can
also be a collection of hosts in other
supported virtualization environments.
virtualization environment
Describes all of the components
associated with a managed system and its
virtualized resources. The associated
components can include a platform
manager, host systems, virtual farms,
virtual servers, and guest operating
systems. The following are examples of
virtualization environments:
1. Microsoft Virtual Server
2. Power Systems that are under the
control of a Hardware Management
Console (HMC)
3. Power Systems that are under the
control of an Integrated Virtualization
Manager (IVM)
4. VMware ESX Server
5. VMware VirtualCenter
6. Xen Virtualization
virtual server
A system composed of partitioned,
shared, or virtualized resources presented
from a host system. An operating system
and other software can be installed on a
virtual server. Terms also used for this
concept are Virtual Machine, Hosted
Computer, Child Partition, Logical Partition,
Domain Guest, Guest Domain, or domU.
vital product data (VPD)
Information that uniquely defines system,
hardware, software, and microcode
elements of a processing system.
volume
A discrete unit of storage on disk, tape, or
other data recording medium that
supports some form of identifier and
parameter list, such as a volume label or
input/output control.
VPD See vital product data.
W
Wake on LAN
A technology that enables a user to
remotely turn on systems for off-hours
maintenance. A result of the Intel-IBM
Advanced Manageability Alliance and
part of the Wired for Management
Baseline Specification, users of this
technology can remotely turn on a server
and control it across the network, thus
saving time on automated software
installations, upgrades, disk backups, and
virus scans.
walk An SNMP operation that is used to
discover all object instances of
management information implemented in
the SNMP agent that can be accessed by
the SNMP manager.
Web Services Description Language (WSDL)
An XML-based specification for
describing networked services as a set of
endpoints operating on messages
containing either document-oriented or
procedure-oriented information.
Windows Management Instrumentation (WMI)
An application programming interface
(API) in the Windows operating system
that enables devices and systems in a
network to be configured and managed.
WMI uses the Common Information
Model (CIM) to enable network
administrators to access and share
management information.
WMI See Windows Management
Instrumentation.
WMI Query Language (WQL)
A subset of the Structured Query
Language (SQL) with minor semantic
changes to support Windows
Management Instrumentation (WMI).
WQL See WMI Query Language.
WSDL
See Web Services Description Language.
Glossary 737
X Zone configuration
A collection of information that describes
XML See Extensible Markup Language.
the zoning for a SAS domain.
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).

738 IBMSystems Director Systems Management Guide




Printed in USA

GC30-4176-03