You are on page 1of 774



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 Resource views . . . . . . . . . . . . 96
Conventions and terminology . . . . . . . . ix Finding systems and other resources . . . . 108
Publications and related information . . . . . . ix Viewing resources in the topology perspective 109
Web resources . . . . . . . . . . . . . xii Working with tables . . . . . . . . . . 114
How to send your comments . . . . . . . . xiii Working with topology maps . . . . . . . 127
Working with properties. . . . . . . . . 139
What’s new in version 6.1 . . . . . . xv Setting navigation preferences . . . . . . . 142
Renaming a resource . . . . . . . . . . 144
Documentation updates as of November 2008 . . xxii
Removing a resource . . . . . . . . . . 145
Terminology changes . . . . . . . . . . xxxi
Managing groups . . . . . . . . . . . . 146
Groups . . . . . . . . . . . . . . 146
Chapter 1. Overview of IBM Systems Creating a criteria-based dynamic group . . . 152
Director . . . . . . . . . . . . . . . 1 Creating a static group . . . . . . . . . 155
Accessibility . . . . . . . . . . . . . . 1 Editing a group . . . . . . . . . . . 156
License information . . . . . . . . . . . . 1 Deleting a group . . . . . . . . . . . 157
IBM Systems Director technical overview . . . . . 2 Adding a resource to an existing group . . . 158
IBM Systems Director components . . . . . . 3 Exporting a group . . . . . . . . . . . 159
Manageable resource types . . . . . . . . 7 Importing a group. . . . . . . . . . . 160
Manageable systems . . . . . . . . . . . 7 Finding and starting tasks . . . . . . . . . 161
User interfaces. . . . . . . . . . . . . 8 Launched tasks and the IBM Systems Director
Base function and extensible plug-ins . . . . . 9 Launched Tasks program . . . . . . . . 161
Upward integration. . . . . . . . . . . 15 Finding a task . . . . . . . . . . . . 162
I’m a 5.20 user. How do I use 6.1? . . . . . . . 16 Starting tasks . . . . . . . . . . . . 163
Why am I starting at the Welcome page? . . . 16 Starting the IBM Systems Director Launched
What can I do with the rest of the interface? . . 30 Tasks program . . . . . . . . . . . . 164
How do I discover my systems? . . . . . . 32 Integrating external applications into IBM
How do I view my systems and groups? . . . 49 Systems Director . . . . . . . . . . . 179
How do I view my inventory? . . . . . . . 67 Scheduling tasks . . . . . . . . . . . . 199
Where are my tasks? . . . . . . . . . . 70 Noninteractive tasks . . . . . . . . . . 199
How do I start tasks? . . . . . . . . . . 71 Jobs and job instances . . . . . . . . . 200
How do I create a hardware event automation Scheduling a task . . . . . . . . . . . 201
plan? . . . . . . . . . . . . . . . 72 Scheduling a task from a selected system . . . 203
Viewing active and scheduled job information 205
Chapter 2. Using the IBM Systems Viewing information about scheduled jobs . . 207
Director Web interface . . . . . . . . 75 Determining target systems that are affected by
Logging into IBM Systems Director Server . . . . 75 a job . . . . . . . . . . . . . . . 208
Logging out of IBM Systems Director Server . . . 76 Viewing job-instance records . . . . . . . 209
Navigating the Web interface . . . . . . . . 76 Viewing job-instance logs . . . . . . . . 210
The Web interface . . . . . . . . . . . 76 Copying a scheduled job . . . . . . . . 212
Customizing the Web interface . . . . . . . 78 Editing a scheduled job . . . . . . . . . 213
Managing and closing open pages in the Web Running a scheduled job immediately . . . . 214
interface . . . . . . . . . . . . . . 79 Suspending and resuming a scheduled job . . 215
Viewing help in the Web interface . . . . . . 80 Deleting a job . . . . . . . . . . . . 216
Navigating IBM Systems Director by way of the Managing auditing . . . . . . . . . . . 217
Welcome page . . . . . . . . . . . . . 80 Audit records . . . . . . . . . . . . 217
IBM Systems Director Welcome page . . . . . 81 Setting server-auditing preferences . . . . . 223
System severity states . . . . . . . . . . 88 Viewing the audit log . . . . . . . . . 225
Starting work in IBM Systems Director . . . . 89 Deleting the audit log . . . . . . . . . 225
Learning about the product . . . . . . . . 90 Encrypting interprocess communication . . . . 226
Checking IBM Systems Director readiness . . . 90 Encryption . . . . . . . . . . . . . 226
Viewing updates. . . . . . . . . . . . 91 Enabling encryption . . . . . . . . . . 228
Viewing tutorials . . . . . . . . . . . 92 Disabling encryption . . . . . . . . . . 228
Viewing the IBM Systems Director Server Changing the encryption algorithm . . . . . 229
summary . . . . . . . . . . . . . . 93 Resending the encryption key to systems . . . 229
Finding and navigating resources . . . . . . . 95 Creating a new encryption key . . . . . . 230

© Copyright IBM Corp. 1999, 2009 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 Adding IBM BladeCenter Integrated Storage
Managing Power Systems running IBM i . . . . 563 devices to a server. . . . . . . . . . . 609
Managing systems controlled by HMC and IVM 564 Provisioning storage from an existing storage
Viewing the Power Systems Management summary 565 subsystem . . . . . . . . . . . . . 610
Monitoring for IBM i message queue events . . . 566 Managing storage volumes in real time . . . . 611
Managing power state settings on IBM Power Configuring iSCSI components in real time . . 614
systems . . . . . . . . . . . . . . . 568 Configuring IBM BladeCenter SAS zone
Power On/Off task support by way of the connectivity in real time . . . . . . . . . 619
operating system on IBM Power systems . . . 568 Managing storage with configuration templates 621
Changing the power state on IBM Power Viewing storage configuration templates . . . 621
systems . . . . . . . . . . . . . . 568 Changing storage configuration templates . . . 621
Creating a configuration template for a storage
Chapter 12. Managing IBM System z volume . . . . . . . . . . . . . . 622
systems. . . . . . . . . . . . . . 571 Managing IBM BladeCenter SAN configuration
mapping . . . . . . . . . . . . . . 622
System z virtualization . . . . . . . . . . 571
Configuring iSCSI components using
Basics about the z/VM operating system . . . . 571
configuration template . . . . . . . . . 626
z/VM manageability access point and agent . . . 574
Managing IBM BladeCenter SAS zone
Viewing the System z Management summary page 575
configuration . . . . . . . . . . . . 630
Discovering systems and collecting inventory data
for System z . . . . . . . . . . . . . . 576
Managing power state settings for Linux on Chapter 14. Managing virtual
System z servers . . . . . . . . . . . . 577 environments . . . . . . . . . . . 635
Power On/Off task support by way of the Virtual systems . . . . . . . . . . . . . 635
operating system on System z servers . . . . 577 Platform managers . . . . . . . . . . 635
Changing the power state on System z servers 577 Virtual farms . . . . . . . . . . . . 635
Hosts . . . . . . . . . . . . . . . 637
Chapter 13. Managing and configuring Virtual servers . . . . . . . . . . . . 638
storage . . . . . . . . . . . . . . 579 Guest-operating-systems. . . . . . . . . 639
Virtualization groups . . . . . . . . . . . 639
Storage management in real time and using
Viewing the virtualization manager summary . . 640
configuration templates . . . . . . . . . . 579
Viewing resources in virtualization perspectives 641
Managing SMI-S providers . . . . . . . . . 579
In the Virtualization Basic perspective . . . . 641
SMI-S providers for IBM Systems Director. . . 579
In the Virtualization Common perspective . . . 641
Installing SMI-S Providers . . . . . . . . 582
In the Virtualization Detail perspective . . . . 641
Configuring SMI-S providers . . . . . . . 587
Viewing resources in the Platform Managers and
Discovering and collecting inventory for storage
Members view . . . . . . . . . . . . . 641
devices . . . . . . . . . . . . . . . 590
Viewing resources in the Virtual Servers and Hosts
Running Discovery and unlocking storage
view . . . . . . . . . . . . . . . . 642
devices using SMI-S providers. . . . . . . 590
Viewing virtualization properties . . . . . . . 642
Running Direct Connection discovery and
Configuring virtual resources . . . . . . . . 643
unlocking storage devices using SMI-S
Configuring Power Systems platform managers 643
providers . . . . . . . . . . . . . . 591
Configuring storage resources . . . . . . . 648
Running Advanced Discovery for multiple
Managing host systems . . . . . . . . . . 650
SMI-S providers using multicast and broadcast . 593
Entering maintenance mode . . . . . . . 650
Running Advanced Discovery for SMI-S
Exiting from maintenance mode . . . . . . 650
providers using a directory agent. . . . . . 594
Starting the virtualization service on a host . . 651
Working with external storage applications . . . 595
Stopping the virtualization service on a host . . 651
Installing and configuring external storage
Managing virtual farms . . . . . . . . . . 651
applications . . . . . . . . . . . . . 596
Adding a host to a virtual farm . . . . . . 651
Launching an external storage management
Creating a virtual farm . . . . . . . . . 652
application . . . . . . . . . . . . . 599
Deleting a virtual farm from IBM Systems
Viewing storage devices . . . . . . . . . . 601
Director and VMware VirtualCenter . . . . . 653
Storage Management Summary . . . . . . 601
Removing a virtual farm from IBM Systems
Viewing storage systems using storage groups 603
Director . . . . . . . . . . . . . . 654
Displaying attached storage for a given system 603
Editing a virtual farm . . . . . . . . . 654
Viewing storage volumes . . . . . . . . 604
Removing a host from a virtual farm . . . . 655
Viewing the health and status of storage devices 604
Starting the virtualization service on a farm . . 655
Storage topology perspective . . . . . . . 605
Stopping the virtualization service on a farm 655
Managing storage in real-time . . . . . . . . 606
Viewing virtual farms . . . . . . . . . 655
Managing IBM BladeCenter and System x
Managing virtual servers . . . . . . . . . 656
storage devices . . . . . . . . . . . . 606
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 .

There are additional supported systems for installation and management.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.1 IBM Systems Director Version 6.0 Updates 6 and 7 for X X X System z systems © Copyright IBM Corp.1 provides many new features and enhancements. Enterprise and Standard x64 Editions X (supports Service Pack 1) Red Hat Enterprise Linux AS.1 server and agents that were not supported in previous releases. New operating systems supported by IBM Systems Director 6. see the IBM Systems Director Hardware and Software Support Guide. In addition. Table 1. For complete list of supported operating systems on each platform. on IBM Power systems X X X Red Hat Enterprise Linux AS. with X Xen Kernel (supports Service Packs 1 and 2) New operating systems supported on IBM Power systems: Red Hat Enterprise Linux AS. 2009 xv .What’s new in version 6. with Xen Kernel (Supports Updates 1 and 2) SUSE Linux Enterprise Server 10.7. version 4. for AMD64 X and EM64T. New operating system support The following table lists operating systems that are supported by IBM Systems Director 6. Hardware support For information about hardware that is supported in this release.1 supports new operating systems and discontinues support for some operating systems that are supported in Version 5. Operating system support IBM Systems Director 6. Enterprise and Standard Editions (supports X Service Pack 1) Windows Server 2008. 1999. 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. some functions have changed in this version and some features have been discontinued. version 5.20. ES. and WS.2. for AMD64 and EM64T.0. see the IBM Systems Director Hardware and Software Support Guide. version 5.

4 system that is to be monitored. 2.5.3 VMware GSX Server.2 Update 1. X X X 2. 2.2 X X Update 1.Table 1. 2.1.5. version 3. and 3. 2.1 and 3. Advanced Server and Server Editions (Service Pack 3 required.0. 2 IBM z/VM Manageability Access Point Agent requires SUSE Linux Enterprise Server 10 for IBM System z. Service Pack 4 X X supported) Windows Small Business Server 2003.3.5.5.3 VMware ESX Server (guest operating systems).3.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. versions 2.5.5.0.5. The agent must be running in a virtual machine within the IBM z/VM.0.2.2.5. version 5.1 server and agents.1 and 3. Table 2.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. 3. 2. 2. 2. versions 3. 2. Windows Small Business Server 2003 R2 X X Red Hat Enterprise Linux AS and ES. version 3.0.2. version 3. versions 2. for Intel Itanium X X Red Hat Enterprise Linux WS.5.5. version 3.1. 2.5. 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.2.5.20 but are not supported by IBM Systems Director Version 6. X X X Service Pack 4 supported) Windows 2000 Datacenter Edition X X Windows 2000 Professional Edition (Service Pack 3 required.4. Discontinued operating systems not supported by IBM Systems Director 6. for AMD64 and EM64T (supports X X Update 9 and earlier) xvi IBMSystems Director Systems Management Guide . and 3.0 (supports Update 9 and earlier) X X X Red Hat Enterprise Linux WS.5. Discontinued operating system support The following table lists operating systems that are supported in Version 5. host operating systems X X VMware GSX Server.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 (supports Update 9 and earlier) X X VMware ESX Server (console).0 to monitor the virtual machines and associated resources known as a z/VM system.4.0.0. 3. New operating systems supported by IBM Systems Director 6. Service Pack 2.1. versions 3.5.

PostgreSQL . 4. collects inventory data about hardware and software.Microsoft SQL Server 2000 . Version 5 Release 3 X X IBM i. Using status manager.0. and visualizes relationships to other systems in the network. 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. and customize the resources and processes to monitor and generate notifications when a custom threshold is reached. 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 4 X X IBM i.Table 2. see the IBM Systems Director Hardware and Software Support Guide. distributes and installs required firmware. Discontinued operating systems not supported by IBM Systems Director 6. device drivers and What’s new in version 6. called plug-ins.4. Update manager Acquires. version 4.5 on IBM Power systems X X X Red Hat Enterprise Linux AS.3. you can create. power status. and 4. versions 5. This includes simple unicast discovery and more advanced discovery workflows to discover. These base plug-ins are provided with IBM Systems Director: Discovery manager Discovers both virtual and physical systems in your network.1 xvii . Functional enhancements v Plug-in architecture: Function has been grouped in to components.0) Databases support v IBM Systems Director Server V6. Status manager Monitors hardware status. authenticate and inventory one or more specific systems in the network.1 (continued) IBM Systems Director Common Platform Operating system Server Agent Agent Red Hat Enterprise Linux AS. view.Microsoft Jet DB For complete information about supported databases.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.DB2/Express – These databases are no longer supported: .1 and X X X 5. Version 6 Release 1 X X Red Hat Enterprise Linux AS. versions 4.1 supports the following newer versions of external databases: – These databases are now supported: . and update compliance status on discovered systems.

IBM Power Systems management Provides full lifecycle management of your IBM Power systems and related resources including discovery. IBM BladeCenter Chassis. configuration and updates. IBM BladeCenter and System x management Provides full lifecycle management of your modular System x. configuration. remote command line. v Web-based user interface: A new flexible. updates. running a task on the management server. IBM System Storage™ management Provides full lifecycle management of your storage resources including discovery. 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. status. 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. status. The virtualization tasks can be included in event automation plans. You can also set up configuration manager to automatically configure newly discovered systems. and web-based remote control for IBM BladeCenter and RSA). including remote control tools (such as Virtual Network Computing (VNC). Improvements include: xviii IBMSystems Director Systems Management Guide . or running a task on the system where the event was generated. You no longer need to install a console. Configuration manager Configures system parameters and hardware settings on systems. and related resources including discovery. Automation manager Automatically performs predefined actions in response to events that occur in your environment using event automation plans. hardware command line. Remote Desktop (RDP). IBM System z management Provides the capability to discover System z systems and their associated virtual servers. and virtualization. updates. including BladeCenter chassis and its installed components. and file transfer tools. and to access status information about them. configuration. in your network. Actions can include sending an email. 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. operating system updates using predefined policies and workflows. status. and virtualization. Remote access manager Provides a set of integrated tools that support remote access. 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. Using update manager.

Organization and related links have also been improved. automatically authenticates discovered systems. event actions. and event logs Tip: Event automation plans were known as event action plans in the previous release. Links from the Web interface display context-sensitive help for the panel that you are currently viewing and also the full help system. – Search capabilities for update documentation files v Event automation plans enhancements: – Simplified interface for managing event automation plans. which identifies the type of resources to discover and the discovery protocols to use. v Update management enhancements: – Compliance policies to verify the currency of updates on systems. – 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. 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. v Online help system enhancements: A new help system is available with advanced search capabilities and an integrated table of contents. 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. and collects inventory data – Improved support for IBM Power. and IBM System Storage systems v System status and health enhancements: – Scoreboard to easily monitor the health of your systems. System z. show relationships between resources. v Security enhancements: What’s new in version 6. event filters. 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. and list resource properties – Navigation links to help you quickly find and perform tasks – New wizards to walk you through certain tasks. including hardware. 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. 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.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. and lifecycle tasks. automation. – Integration of IBM Systems Director Navigator for i5/OS into IBM Systems Director Web interface. inventory. status. including the seamless integration of Storage Configuration Manager and the ability to launch external applications from the Web interface. For more information. v Storage management enhancements: – Seamless integration of Storage Configuration Manager (SCM) function – Ability to launch storage management application. – New commands for systems. such as TotalStorage® Productivity Center (TPC)). user administration. user administration. – Ability to specify credentials for a specific protocol or system. xx IBMSystems Director Systems Management Guide . v Platform management enhancements: – Support has been improved for managing your storage products. see IBM Systems Director Commands Reference. inventory. including launching Virtual Network Computing (VNC) and Remote Desktop (RDP). status. However. to use the command syntax supported in IBM Director version 5. scheduler. see IBM Systems Director Commands Reference. 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. health. process management and resource monitoring. 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. user administration. scheduler. The dircli command-line interface is supported in this release for backward compatibility.20 and earlier. For a complete list of commands. automation. SNMP agent settings. and permissions v System configuration enhancements: – Integrated operating-system configurations settings for network. 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. – Ability to launch IBM Systems Director Console for AIX from the IBM Systems Director Web interface. you must set the CLILEGACY environment variable. All smcli commands will run using either smcli or dircli. and inventory data – Ability to create. roles. process management and resource monitoring commands: The command-line interface has been enhanced with new commands to support systems. and to view and edit credentials on specific systems – New command line support for user groups.

and the number of available licenses.Send an Event Message to a Console User .Add a Message to the Console Ticker Tape . build a software package. memory usage.20 is not supported in this release: – License administration is not supported: License Administrator is no longer supported in IBM Systems Director. generate performance-analysis reports. identify current or potential bottlenecks. – ServeRAID™ Manager extension is not supported: ServeRAID Manager is no longer a supported extension of IBM Systems Director.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.Update the Status of the “event” System v IBM Director V5. – Microsoft Cluster Management is not supported: You can no longer monitor the status of clusters in your network using the Microsoft Cluster Browser. hard disk capacity. – Discontinued event actions: These event actions have been discontinued: . recommend ways to improve performance and prevent diminished performance or downtime. or clusters. The commands are now called storage commands. 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. System Availability was an What’s new in version 6. Tip: You can launch the ServeRAID Manager as an external application from the IBM Systems Director Web interface. and raise events for RAID controllers.1 xxi . however. In the previous release. In the previous release. you used Rack Manager to group your systems in visual representations of rack suites. groups. and distribute the package to managed systems. – High availability is not supported: High availability configurations are not currently supported by IBM Systems Director. the application does not recognize IBM Systems Director systems. – Associations are no supported: Associations changed the organization of a group of managed objects. – 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). – Rack management is not supported: Rack Manager is no longer supported in IBM Systems Director. and network traffic). This is not longer supported.Discontinued function v IBM Director base function: The following base function that was available in IBM Director V5.20 extensions The following extensions that were available in IBM Director V5. IBM Systems Director does perform inventory collection. Capacity Manager was a resource-management planning tool that you can use to monitor critical resources (for example processor usage. – Software Distribution Premium Edition extension is not supported: Software Distribution Premium Edition is no longer a supported extension of IBM Systems Director. – System Availability is not supported: System Availability is no longer a supported extension of IBM Systems Director. monitor status. you used License Administration to view the total number of product licenses. Software Distribution Premium Edition was used to import applications and data. the number of used licenses.

identify problematic systems that have had too many unplanned outages over a specified period of time. v The English documentation is updated more frequently than the translated documentation.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 Service and Support Manager plug-in. rely on the English documentation. 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. – The name of the Service and Support Manager plug-in is incorrectly called Electronic Service Agent™ in the online help. z/VM Center used the z/VM hypervisor to provision System z resources in form of z/VM virtual servers. see IBM Systems Director Commands Reference. when discrepancies occur between translated documentation and the English documentation. These corrections are not available in the online helps that are viewable from the IBM Systems Director Web interface. The bold text is the title of the topics that have changed. xxii IBMSystems Director Systems Management Guide . The following sections identify the corrections that have been made to specific topics in the IBM Systems Director documentation. identify system that have old availability data. The helps incorrectly state that it is a free plug-in.20. identifies and reports hardware problems and service information automatically to IBM® for service and support. 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. analysis tool that you used to view statistics about system uptime and downtime. v “Web resources” on page xii: Information and a URL for the IBM Systems Director Best Practices wiki has been removed.ibm. v “Platform Agent” on page 6: This topic changed to indicate that Platform Agent is equivalent to IBM Director Core Services 5. In most cases. 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. – z/vm Center extension is not supported: z/vm Center is no longer a supported extension of IBM Systems Director. This wiki does not exist. 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. 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. The IBM Systems Director information center includes updates to both the printed and online documentation. equivalent functionality is implemented through commands in the smcli command-line interface.20.3. and identify system that fail to report data.20 and earlier are no longer supported. For a complete list of supported commands. which includes the Electronic Service Agent tool. not 5.

html): This topic has been updated to indicate that PTF MH01146 is required for Hardware Management Console Version 7. Discovering and inventorying systems v “Discovery profiles” on page 239: This topic has been updated with a description of the default advanced discovery profiles.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 exported.3 SP2. They are displayed in the Power Server group that is contained in the IBM Power Systems group. and redbooks have been added to the information center.1. 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. Configuring after installation v “Configuring the command line interface” (publib. 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.1 xxiii .ibm. Installing v Extensive changes have been made to most of the installing topics.v “Publications and related information” on page ix: Links to PDFs. For the Power Servers group Note: The JS21 and JS22 blade servers are displayed in this group also. v “Exporting a group” on page 159: This topic has changed to also include static groups.ibm.3. a new command-line utility that is available for migrating data from IBM Director 5.boulder.1/ fqm0_r_supported_virt_software_versions. Both static and dynamic groups can be imported. These links are not in the online help. What’s new in version 6. 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.20 to a new installation of IBM Systems Director 6. white papers.plan_6.configdir_6.com/infocenter/systems/topic/director.boulder.1/ fqm0_t_cm_configuring_cli. Planning v “Virtualization software supported by IBM Systems Director” (publib.com/infocenter/systems/topic/director.

exe. The volume name will be made by appending a unique number to this prefix. For Local Storage. for example notepad. 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 . 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. The remote Xen server or host must be started and have access granted in order to establish communications. 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. The IP address that IBM Systems Director has for the system is used to launch the Web browser with http protocol. so a command line window opens when it is started. is not supported. 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.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. capacity information collected for storage devices attached to systems that are running IBM Director 5. which you can use to access a system that has a Web server. You can use the remote Xen console window to establish a fully active command session with a remote Xen server or host. 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 Total usable capacity and Total available capacity is not included in the Capacity Summary for these storage devices.Opens a browser window for the selected system Remote Xen Console .20 is limited to the Total raw capacity. 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. This field must be ten or fewer xxiv IBMSystems Director Systems Management Guide . which is a command-line interface to a remote Xen server. This session is non-graphical. v “Remote Xen Console” on page 450: This is a new topic that describes the Remote Xen Console tool. 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. 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.

used for IBM TotalStorage DS4000® storage systems. 3. If this field is not specified. numbers.1 xxv . 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. 7. on Linux and AIX systems. such as Windows_Installer-WS32-10.1. v “Managing IBM BladeCenter SAS Connectivity Modules and their attached storage devices” on page 608: Steps 2.1. Instructions for installation on Windows systems already existed.30.35. This field must be ten or fewer characters consisting only of letters.0 Windows. These should be used unless they have been changed. and the underscore character. 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.1. numbers. but the installation will complete with errors and you will not be able to use the subagent.0 Linux or PlatformAgentSubagent IBM BladeCenter SAS RAID Controller Module 6. The default User ID and Password are USERID1 and PASSW0RD (with a zero). v “Managing IBM BladeCenter Integrated RAID Controllers and their attached storage devices” on page 607: Steps 4 and 7 have been deleted. and 13 have been deleted. The volume name will be made by appending a unique number to this prefix. 4. 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.00. 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.0 Linux or PlatformAgentSubagent IBM BladeCenter SAS RAID Controller Module 6. characters consisting only of letters.0 Windows Before installing the PlatformAgentSubagent IBM BladeCenter SAS RAID Controller Module 6. It is possible to install the subagent without this prerequisite. 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. What’s new in version 6. 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. 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. The InstallAnywhere welcome page is displayed. the first ten characters of the host name are used.exe. 10. 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 first ten characters of the host name are used. If this field is not specified. and the underscore character. ensure that you have already installed Platform Agent on the managed system.1.

1. 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. you cannot select a protocol. . the default port number is 5988. 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. the default port number is really 15988. v “Requirements for ServeRAID Manager” on page 601: Extensive changes have been made to this task. However. 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. 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.If you selected a Hardware type of IBM system storage DS3000/DS4000. the default port number displayed will be 5988. xxvi IBMSystems Director Systems Management Guide .If you selected a Hardware type of IBM BladeCenter S SAS RAID Controller Module. depending on the operating system that hosts this SMI-S provider. http protocol will always be used. and each of these Platform-Agent managed systems can also manage a maximum of four IBM BladeCenter chassis. This might not be correct. when this SMI-S provider is running on Linux. This provider has one of the following names: PlatformAgentSubagent IBM BladeCenter SAS RAID Controller Module 6. This provider is installed automatically with IBM Systems Director Server on supported operating systems.1. This provider can be copied to Platform-Agent managed systems if the need arises.0 Linux or PlatformAgentSubagent IBM BladeCenter SAS RAID Controller Module 6.0 Windows The provider for the IBM BladeCenter S SAS RAID Controller Module can work with a maximum of four IBM BladeCenter chassis. 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. and you must change the value to 15988 in order to use the default port on Linux. Review these choices and correct the port number if necessary. – Two new steps were added between Step 14 and Step 15: . Run Inventory Collection on the Agent to get the Integrated RAID Controller. v “Installing and configuring ServeRAID Manager” on page 598: Extensive changes have been made to this task. 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.

htm v “mkfarm command” (publib.ibm.com/infocenter/systems/topic/director.1/ fqm0_r_cli_mkrelocatetask. 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.htm v “mkrelocatetask command” (publib.com/ infocenter/eserver/v1r2/topic/eica7/ eica7_reference_command_info_commands. Commands reference v --help option: The following tip has been added to --help option that appears in every command description for displaying man pages.ibm.2 information center was incorrect.com/infocenter/systems/topic/director. The correct URL is: What’s new in version 6.cli_6. v “chfarm command” (publib.com/ infocenter/eserver/v1r2/topic/eica7/ eica7_reference_command_info_commands. The correct URL is: publib.1/ fqm0_r_cli_chfarm.1 xxvii .ibm. 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 “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. Security v “Configuring the authentication registry” on page 711: This topic has been added. Tip: (AIX and Linux only) You can also display detailed help in the form of man pages using the man -t command_name command.2 information center was incorrect.cli_6.boulder. This note is not in the man pages or command line help.boulder. v “Live relocation” on page 679: This topic has changed to reflect that Xen no longer requires the virtualization manager subagent.com/infocenter/systems/topic/director. Troubleshooting v Changes have been made to several topics and many topics have been added to this section.boulder.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.ibm.ibm.boulder.1/ fqm0_r_cli_mkfarm. v “Authenticating IBM Systems Director users stored in LDAP” on page 691: The steps in this topic have changed significantly.cli_6.boulder.html): The URL for the IBM® Virtualization Manager v1.2 information center was incorrect. The correct URL is: publib.html): The URL for the IBM® Virtualization Manager v1.html): The URL for the IBM® Virtualization Manager v1.

cli_6.cli_6.boulder.com/infocenter/systems/topic/director.cli_6.boulder.html): The syntax in the second example has been corrected. The correct URL is: publib.server command” (publib.boulder.ibm.htm v “chusregp command” (publib.com/infocenter/systems/topic/director.boulder.com/infocenter/eserver/v1r2/topic/eica7/ eica7_reference_command_info_commands. v “mknspath command” (publib.ibm.com/infocenter/systems/topic/director.1/ fqm0_r_cli_mkcfgtmpl.ibm.1/ fqm0_r_cli_lsjobhistory. .cli_6.ibm.ibm. 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.ibm.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.cli_6.com/infocenter/systems/topic/director.cli_6.server command.boulder. smclichusergp -e role2:group1.html): The follow description has been removed: If you do not specify any listing options.html): This is a new topic that describes the dirinstall.cli_6.com/infocenter/systems/topic/director.ibm. not a comma. v “discover command” (publib.boulder.group2 mygroup v “dirinstall.1/ fqm0_r_cli_virtualization_cmds.html): The syntax for the discover command incorrectly placed the [-t system_type] option before the [-i ip_address_list] option.1/ fqm0_r_cli_mknspath.2 information center was incorrect. The delimiter between the group names should be a semicolon (.1/ fqm0_r_cli_dirinstall_server.).1/ fqm0_r_cli_lstask.com/infocenter/systems/topic/director.html): In the syntax.1/ fqm0_r_cli_discover. .com/infocenter/systems/topic/director.ibm.61: The input XML is not valid.com/infocenter/systems/topic/director.ibm.ibm.com/infocenter/eserver/v1r2/topic/eica7/ eica7_reference_command_info_commands. publib.boulder.htm v “Virtualization commands” (publib. This command is used to install IBM Systems Director on a management server running AIX or Linux.1/ xxviii IBMSystems Director Systems Management Guide .com/infocenter/systems/topic/director. 0x3D v “mkcfgtmpl command” (publib.html): – The following return codes have been added: .boulder. 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.cli_6.html): The URL for the IBM® Virtualization Manager v1.boulder.1/ fqm0_r_cli_chusergp.58: A template with the specified name and subtype already exists.ibm.boulder. v “lstask command” (publib. this command lists job names and the job-instance IDs for those jobs.cli_6. -wip_address_list has been changed to -i ip_address_list.boulder.125:An internal error occurred.

com/infocenter/systems/topic/director.1 xxix . v “Storage Volumes page” (publib.html) User interface reference v “Import Groups window” (publib. fqm0_r_cli_smreset.html): The description of the Volume prefix field in the Fields section has changed.ibm.1/ fqm0_r_cli_smexport.html): Two new options have been added to this page: Launch Web browser . and the underscore character.com/infocenter/systems/topic/director. v The following commands have been added as part of the IBM Systems Director Migration Tool command-line utility: – “smexport command” (publib.com/infocenter/systems/topic/director. This field must be ten or fewer characters consisting only of letters. numbers.20 is limited to the Total raw capacity column.boulder.1/ fqm0_r_panel_remote_access_summary_page.1/ fqm0_r_panel_rn_location_properties.com/infocenter/systems/topic/director.console_6. If this field is not specified.ibm.remote_6.1/ fqm0_r_cli_smimport.html) – “smimport command” (publib.1/ fqm0_r_panel_storage_boot_bundle.ibm.boulder. The Total usable capacity and Total available capacity columns are zero.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.com/infocenter/systems/topic/director.boulder. the first ten characters of the host name are used. v “Remote Access Summary page” (publib. The -l option displays verbose messages and a non-zero exit status to standard output.storage_6.1/ fqm0_r_panel_create_volume_page.boulder.com/infocenter/systems/topic/director.com/infocenter/systems/topic/director. numbers.console_6.boulder. and the underscore character.1/ fqm0_r_panel_import_groups.ibm. the following limitation has been added to the Local storage row for the Total usable capacity and Total available capacity columns.boulder.Communicates with a remote Xen server or host v “Storage Management Summary page” (publib. This is the default port number for remote presence.ibm.storage_6.html): The description of the Volume prefix field in the Fields section has changed. Both static and dynamic groups can be imported. If this field is not specified.com/infocenter/systems/topic/director. v “Location window” (publib.html): This topic has changed to also include static groups.1/ fqm0_r_panel_storage_management.cli_6.cli_6.ibm. What’s new in version 6. v Management Module Ports Configuration page: Remote presence port information has been added. The default value is 3900.ibm.Launches a Web browser for a system that hosts a Web server Remote Xen console .boulder. v “Create Volume page” (publib. This field must be ten or fewer characters consisting only of letters.html): The -l option has been added to the syntax and option description. Capacity information collected for local storage devices attached to systems that are running IBM Director 5.storage_6.html): In the Capacity Summary section.boulder. the first ten characters of the host name are used.ibm.

status_6.boulder. v “Process Management page: Applications page” (publib.ibm.status_6. if you specify a resend value between (but not including) 0 and 5 seconds.boulder.ibm.boulder.ibm.status_6. which you can use to define a monitor or an event threshold for a specified process.html): The following option and associated text has been removed from this topic: Monitors → Process Monitors Displays the Process Monitors page. for example notepad.ibm. v “Process Management page: Servers page” (publib.html): In this topic.ibm.status_6. v “Threshold page” (publib. v “SNMP Browser page” (publib.boulder. is not supported.ibm.status_6.status_6.1/ fqm0_r_panel_activate_edit_thresholds.com/infocenter/systems/topic/director.1/ fqm0_r_process_management_window_services_page.com/infocenter/systems/topic/director. the section xxx IBMSystems Director Systems Management Guide .boulder.com/infocenter/systems/topic/director. the minimum polling time on the server is five seconds.com/infocenter/systems/topic/director.1/ fqm0_r_process_management_window_servers_page.1/ fqm0_r_panel_command_automation.html): The following option and associated text has been removed from this topic: Monitors → Process Monitors Displays the Process Monitors page.ibm.1/ fqm0_r_panel_snmpb_snmp_browser_window.boulder.boulder. v “Process Management page: Subsystems page” (publib.com/infocenter/systems/topic/director.1/ fqm0_r_process_management_window_subsystems_page. the server will automatically resend events only once every five seconds. which you can use to define a monitor or an event threshold for a specified process.html): This topic has been updated to include the following note with the ″Resend delay″ definition: Note: Other than zero.html): The following option and associated text has been removed from this topic: Monitors → Process Monitors Displays the Process Monitors page.ibm.html): A note was added to this topic stating that using the command automation task to launch interactive programs. which you can use to define a monitor or an event threshold for a specified process.com/infocenter/systems/topic/director.status_6. So.com/infocenter/systems/topic/director. v “Command Automation page” (publib.html): The following option and associated text has been removed from this topic: Monitors → Process Monitors Displays the Process Monitors page.1/ fqm0_r_process_management_window_device_services_page.status_6.html): The following option and associated text has been removed from this topic: Monitors → Process Monitors Displays the Process Monitors page.1/ fqm0_r_process_management_window_applications_page.boulder.com/infocenter/systems/topic/director. which you can use to define a monitor or an event threshold for a specified process.exe. which you can use to define a monitor or an event threshold for a specified process. v “Process Management page: Services page” (publib. v “Process Management page: Device Services page” (publib.

and management function. perform limited remote access. additional event support. and varies based on operating system and hardware: discover systems. IBM Director Core Platform Agent Platform Agent provides a lighter footprint Services and fewer management functions than the Common Agent.security_6. monitor health and status. remotely deploy and install Common Agent. perform power management function. v “Configure Access page” (publib.boulder. perform remote access. v “SNMP Management page” (publib. deployment. 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. The function available for Common-Agent managed systems varies based on operating system and hardware. manage alerts. The function available for Platform-Agent managed systems is limited to the following tasks.com/infocenter/systems/topic/director. collect limited platform inventory data. manage operating system resources and processes.1 xxxi .status_6. monitor processes and resources. Deprecated terms New terms Description IBM Director Agent Common Agent Common Agent provides a rich set of security. manage alerts. remotely deploy and install Common Agent. and set critical thresholds that send notifications when triggered.1/ fqm0_r_panel_snmpb_snmp_browser_page.com/infocenter/systems/topic/director. collect comprehensive platform and operating system inventory data.ibm. and the introduction paragraph has been updated to to remove mention of setting community names and attributes. including transferring files. about right-click options has been removed and topic.boulder. Terminology changes Several terms have changed in IBM Systems Director V6. and includes the following tasks: discover systems.ibm. monitor health and status.1. and perform limited restart capabilities.html): Mention of setting community names and attributes in the description for the ″SNMP Browser″ action has been removed from this topic.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.1/ fqm0_r_panel_basic_configure_access.

An event action plan comprises one or more event filters and one or more customized event actions. Remote session Remote command A command-line interface to a remote line system. and perform limited restart capabilities Managed object System A hardware endpoint that can be discovered and managed by IBM Systems Director. or Simple Network Management Protocol (SNMP). For example. IBM Hardware Management Console (HMC). Hardware control Platform manager Software that manages one or more host point systems and their associated virtual servers and operating systems. physical servers. Event action plan Event automation A user-defined plan that determines how plan IBM Systems Director automatically handles certain events. Job activation Job instance A specific occurrence of a job that is running or has completed running. Extension Plug-in Free or for-fee software that is downloaded and installed on top of IBM Systems Director to provide additional function. perform limited remote access. Platform managers can be started from the IBM Systems Director Web interface. 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). IBM Integrated Virtualization Manager (IVM). The function available to Agentless-managed systems is limited to the following tasks. network devices. storage devices. and virtual farms are systems. and varies based on operating system and hardware: discover systems. For example. BladeCenter Management Module. collect limited operating-system inventory data. 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. remotely deploy and install Common Agent and Platform Agent. and VMware VirtualCenter are platform managers. Distributed Component Object Model (DCOM). xxxii IBMSystems Director Systems Management Guide . virtual servers.

Overview of IBM Systems Director This section provides an overview of IBM Systems Director. technical overview. To install additional agent components on non-IBM® x86 systems. you are entitled to install the agent component on only 20 non-IBM® x86 systems. Accessibility IBM® strives to provide products with usable access for everyone. These 20 licenses for non-IBM® x86 systems are not transferable and cannot be combined or aggregated. ensure that you have the necessary licenses. © Copyright IBM Corp. If you choose to install and use a different supported database. 1999. and what is new in this release. You can purchase licenses from the Ready to Buy Web Page at www. ensure that you have obtained any required license for the installation. You are not authorized to run IBM Systems Director Server on non-IBM® systems. 2009 1 . Notwithstanding the foregoing. See the hardware and software requirements for more information about supported systems. supported hardware and software requirements. web resources. the IBM Systems Director includes a license for up to 20 installations of the agent component on non-IBM® x86 systems. including release notes. Database IBM Systems Director Server uses a database to store data. you must obtain additional agent component licenses from IBM®. You are authorized to use management server and agent components only on IBM® systems. License information Before deploying this product. if you buy two IBM® systems and install IBM Systems Director on only one of them. For example. You are authorized to manage non-IBM® systems that run Platform Agent and non-IBM® systems without an agent.com/systems/ management/director/buy/ IBM® may audit your compliance with these terms upon reasonable advance notice to you. You can use the Apache Derby database that is included with IBM Systems Director without obtaining additional licenses. regardless of age or ability. IBM Systems Director IBM Systems Director contains management server and agent components. your entitlement is limited to managing 20 non-IBM® x86 systems. If you install IBM Systems Director on both IBM® systems.Chapter 1.ibm. and you are authorized to use the components on IBM® systems.

and Linux on POWER® operating systems v IBM BladeCenter and System x management – IBM BladeCenter chassis components. Through a single user interface. and LS41 and QS21 blade servers – AIX. 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. determining how these systems relate to one another. 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. such as switch modules and server blades – System x systems and blade servers – VMWare. A set of common tasks included with IBM Systems Director provides many of the core capabilities required for basic management. Microsoft Virtual Server (MSVS). Power blades. configuration. event notification and automation across managed systems. with multiple operating systems and platforms. IBM i. By using industry standards.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. 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 . inventory. IBM Systems Director provides consistent views for viewing managed systems. IBM Systems Director supports multiple operating systems and virtualization technologies across IBM® and non-IBM® x86 platforms. and VIOS appliances – Power servers. thus helping to correlate technical resources with business needs. IVM. system health. monitoring. updates. and identifying their statuses. These common tasks include discovery. The systems supported include: v IBM Power Systems management – HMC. which means instant out-of-the-box business value. up to 5 000 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.

such as IBM BladeCenter SAS. – Network storage. IBM Systems Director components IBM Systems Director includes IBM Systems Director Server and two operating-system agents: Common Agent and Platform Agent. and BladeCenter Management Module). This figure shows where the IBM Systems Director Server and operating-system agents are installed in a basic IBM Systems Director environment. NetIQ. Overview 3 . Hewlett-Packard. IBM Systems Director Server provides a central point of control for aggregating and managing discovered systems based on a service-oriented architecture. called systems. that can be discovered and managed by IBM Systems Director. It can be installed on one or more 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). and set of management functions. Computer Associates. Qlogic. and BMC Software. such as DS3000. and DS6000™ – Storage switches. but the level of management is limited. Systems that connect to the IBM Systems Director Web interface on the management server through a Web browser are called browser systems. DS4000. Baseboard Management Control (BMC). Each agent provides a different footprint size. IBM Systems Director can discover and manage some systems on which neither of these operating-system agents is installed. Brocade. Nortel and Cisco IBM Systems Director integrates with robust workgroup and enterprise management software from IBM® (such as Tivoli® software). The level of system management depends on the agent that is installed on the system: Common Agent or Platform Agent. level of performance. Chapter 1. called management servers. These agents run on operating-system-based and hardware-based endpoints. Microsoft.

You can access information that is stored in this database even when the managed systems are not available. It provides a central point of control for aggregating and managing discovered systems based on a service-oriented architecture.Common Agent installed on each FQM0501-0 Figure 1. Management server IBM Systems Director Server installed Includes: .Command-line Interface . Apache Derby.no IBM Systems Director Ccode installed Ccode installed Cco Platform managed systems .Common Agent HTTPS TCP/IP Various protocols Browser system SNMP devices . Software in an IBM Systems Director environment Management server The management server is a system that has IBM Systems Director Server installed. and their relationships to other resources in a relational database. IBM Systems Director Server stores data about discovered systems.Platform Agent installed on each Common managed systems .no IBM Systems Director . their attributes.no IBM Systems Director Ccode installed Agentless managed systems Agentless managed systems . 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. although you can choose to use any supported database (including the high-performance DB2® database). The system that you use to interact with these interfaces is called the browser system. IBM Systems Director Server includes a default database.IBM Systems Director Server . 4 IBMSystems Director Systems Management Guide .IBM Systems Director Web interface .

IBM® System z systems. the term Common Agent (with both words capitalized) refers to the IBM Systems Director Common Agent.Tip: When you install IBM Systems Director Server.20. deployment. Overview 5 . The function available for Common-Agent managed systems varies based on operating system and hardware. because the Common Agent requires you to keep fewer ports open. These systems cannot be managed with Platform Agent. when the system is running a supported operating system. and set critical thresholds send notifications when triggered v Manage operating system resources and processes v Manage updates Additionally. IBM BladeCenter. Common Agent is available for all IBM® Power Systems. see the Planning information. Common Agent has a single run-time that can be shared by IBM Systems Director and Tivoli products. IBM Systems Director supports systems running Level 2: Common Agent and IBM Director Agent version 5. and management function. 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. Common Agent Common Agent provides a rich set of security. deployment. see the Planning information. including transferring files v Perform power management function v Additional event support v Monitor processes and resources. It is also supported by other management products that use the IBM Tivoli Common Agent Services management infrastructure version 1. reducing the demands on IBM Systems Director Server. such as Tivoli Provisioning Manager. Note: Throughout the IBM Systems Director documentation.1 or later. IBM® System x. Notes: v Systems running AIX require the Common Agent to be installed. Common Agent replaces Level 2: IBM Director Agent version 5. which includes subagents that provide specific management capabilities for Chapter 1. too. and some non-IBM® systems.20. v For a detailed list of operating systems that are supported for Common Agent. For a detailed list of function that is supported by Common-Agent managed systems. support shared credentials. Firewall management is simplified. and management function. and drive common services.4. The Common Agent provides a rich set of security. to reduce the agent footprint. using Common Agent instead of Platform Agent provides enhanced scalability through asynchronous system management. the Common Agent is installed automatically on that system.

lowercase text is used. 6 IBMSystems Director Systems Management Guide .3. Platform Agent is equivalent to Level 1: IBM Director Core Services version 5. Agentless-managed systems must support the Secure Shell (SSH) or Distributed Component Object Model (DCOM) protocol. IBM Systems Director supports systems running IBM Director Core Services version 5.20. and varies based on operating system and hardware. firmware and driver updates and remote deployment. When referring to these common agents generically. System x and IBM BladeCenter.3. Platform Agent is part of the Universal Manageability Enablement (UME) in the base operating system. These Agentless-managed systems are best for environments that require very small footprints and are used for specific tasks. It provides a subset of Common Agent function used to communicate with and administer the managed systems. or the Simple Network Management Protocol (SNMP) interface. By default. Platform Agent Platform Agent is well suited for environments that require a smaller footprint without sacrificing a high level of manageability. IBM Systems Director uses the range of addresses that are in the IP domain of the management server. 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. IBM System Storage systems.20. You can discover a specific IP address or range of IP addresses using the IBM Systems Director Web interface. including hardware alerts and status information. Platform Agent is available for all IBM Power. For IBM i. 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. and some non-IBM® systems. 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. see the Planning information in the information center at. The function available for Platform-Agent managed systems is limited to the following tasks. Note: The versioning for Platform Agent might not match the versioning of IBM Systems Director. 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. and System z. IBM Systems Director. such as one-time inventory collection.

storage systems. you can view the All Systems group to work with all discovered systems. you can use the All Systems or Virtualization Systems groups to work with the physical aspects of a system. A submenu of applicable perspectives is displayed. Agentless-managed systems are well suited for one-time collection of inventory. When an Agentless-managed system is discovered. either by using a dual-boot feature or by way of a hypervisor. click Actions > Topology Perspectives. virtual servers. Hardware-based systems are the physical and virtual systems. From the Web interface. and updates are all resources. Operating-system-based systems (referred to as operating systems) consist of the operating system image. 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. agent. v Discover systems v Collect limited operating-system inventory data v Remotely deploy and install Common Agent and Platform Agent. and network devices. You can also use the topology map to view the relationship between systems. and can be used for updating firmware and drivers. Overview 7 . groups. and varies based on operating system and hardware. Manageable systems A system is one type of resource that IBM Systems Director manages. it is locked by default. see the Planning information in the information center at. you can use the Find a Resource task to find resources and use the Navigate Resources task to view and work with these resources. and determine how many operating systems are running on a physical system. determine how many virtual servers a physical system contains. A submenu of applicable related resources is displayed. IBM Systems Director manages these types of systems: Chapter 1. and remotely deploying and running it via SSH or DCOM services. you can view the All Operating Systems group to work with these types of systems. drivers. To view the topology map view for a system. From the Navigate Resource page in Web interface. applications. v Perform limited remote access v Perform limited restart capabilities For a detailed list of function that is supported by Agentless-managed systems. slots. The function available to Agentless-managed systems is limited to the following tasks. You can unlock the system by requesting access to it through IBM Systems Director. For example. From the Navigate Resource page in Web interface. Manageable resource types A resource is a generic term for anything that IBM Systems Director can manage. systems. From the Navigate Resource page in Web interface. Physical systems can host multiple operating systems and virtual servers. To view resources associated with a system. cards. such as servers. click Actions > Related Resources. and configuration settings. Note: No persistent data is stored on Agentless-managed system.

optimize resource utilization. The system on which you logged into the IBM Systems Director Web interface is referred to as the browser system. 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. and improve IT flexibility and responsiveness. If you use port 8422. The default ports for the Web server are 8421 and 8422. Data is securely transferred between the Web browser and Web interface through HTTPS. After IBM Systems Director discovers a physical server. Tip: Virtual servers running on IBM® systems are often referred to as logical partitions or virtual machines. Using virtualization. make sure that you specify https to indicate a secure port. 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. it continues the discovery process to find all associated virtual servers. Each IBM® system offers virtualization technologies to help you consolidate systems. 8 IBMSystems Director Systems Management Guide . 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. optimize resource usage. Each virtual server has an independent operating environment and can have functions or features that are not available in its underlying physical resources. you can create multiple discoverable virtual servers from a single physical server or create a single discoverable virtual server from multiple physical servers. and improve IT flexibility and responsiveness.

network. the CLI runs only on the management server. You can run the CLI remotely using a remote-access utility. the task can be displayed in one of the following ways: v In another instance of your Web browser. For security reasons.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. The task provides its own Web interface. This application is called the IBM Systems Director Launched Tasks program. Overview 9 . 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 . Plug-ins that provide advanced function or function tailored to a particular environment can be downloaded and installed on top of IBM Systems Director. v The IBM Systems Director Launched Tasks program is displayed and opens the task that you selected. storage. such as secure shell (SSH) or Telnet. and agent management functions include: Chapter 1. Because the IBM Systems Director Launched Tasks program opens outside of the IBM Systems Director Web interface. Basic user interface. the CLI runs only on the management server. When you select a launched task. IBM Systems Director provides some tasks that still require a client-based application. security. v As a separate program on your system desktop. v For security. see “Downloading Java Web Start. For more information. Base function and extensible plug-ins Base plug-ins in IBM Systems Director provide core function to manage the full lifecycle of IBM servers. The command-line interface follows the GN/POSIX conventions. Java™ Web Start (JWS) is also provided for installation. Tips: v The IBM Systems Director smcli supports most commands that were available in previous releases through the discontinued dircli utility. and virtual servers. These tasks are launched tasks and are identified on menus by the Launched tasks icon . 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.” Command-line interfaces You can use the systems management command-line interface interactively using the smcli utilities. IBM Systems Director provide some tasks that start outside of the IBM Systems Director Web interface.

groups. inventory data. Discovery manager Discovery manager performs physical and virtual system discovery and inventory of related resources on the network. navigating to a specific resource.20 to a current agent on existing systems. 10 IBMSystems Director Systems Management Guide . and security) and processes. operating systems. including relationships and properties v Organizing logical sets of resources into groups v Starting. 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.. and network. and farms). virtual servers. stopping. This includes simple discovery using a single IP address or host name or a range of IP addresses. and network devices) in a heterogeneous environment. and virtual hardware (such as virtual systems. upgrading from IBM Director Agent version 5. You can use the discovery manager plug-in to: v Discover systems such as physical and virtual servers. even when services span different systems v Installing agents on new systems. or using the new capabilities integrated into the command line interface. and tasks v Managing credentials to support single sign-on authentication. Lightweight Directory Access Protocol (LDAP). firmware and BIOS. v Collect inventory data about hardware and software that is currently installed on systems. 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. software applications. You can also use a discovery profile to discover one or more systems of different types and protocols.20 or IBM Director Core Services version 5. The status of discovered systems is automatically retrieved and displayed. diagnostic information. and this display can be customized in several ways—using one of the system health and status-related tasks. v Finding and viewing resources and resource information. v Manage inventory profiles that you can use to discover a group of resources or collect inventory data based on a set of criteria. Inventory data is information about physical. applications. or domain controller v Creating roles and authorizing users and user groups to access certain systems. logical. operating systems. storage systems. v View systems. middleware. and promote an Agentless-managed system or Platform-Agent managed system to a Common-Agent managed system.

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. You can also identify events to be cleared automatically. configure systems after installation. compliance.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 Identify problems and find the root cause by viewing problems and the event log. scoreboard. Overview 11 . and dashboard. and powered on. as a result of an event or as part of a workflow that the configuration needs to be support). A configuration plan is a set of templates that can be applied to one or more systems in a specific order. The health summary shows the overall health of your managed systems. Automation manager Automation manager provides tools to notify an administrator or run a predefined tasks automatically when a certain event occurs. v Monitor system information in various formats. Configuration manager Configuration manager is used to integrate new hardware into your environment. allocated. and performance of managed systems in your environment using the health summary. and network resources even if the resources are comprised of very different technologies. The scoreboard summarizes the hardware state. v Monitor dynamic properties of resources by defining monitors and thresholds and generating a notification when a threshold has been reached. A configuration template is a collection of settings and values that define the configuration of a system. v Initially configure one or more systems (hardware and operating systems) to a point where they can be deployed. v Determine the health. or do one-off configurations for problem resolution. 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 Monitor processes and device services on a specific system by defining monitors and thresholds and generating a notification when a threshold has been reached. or re-provisioning (for example. v Reconfigure systems to prepare for redeployment. reallocation. event state and compliance state for all managed systems. Configuration manager leverages a set of well defined templates that can be applied to servers. v Automatically configure newly discovered systems using the automatic-deploy capability of a configuration plan. v View the event log. v Manage configuration templates and plans. Chapter 1. storage. v Drill down into the root cause of problems. The dashboard shows performance metrics for specific managed systems. v Subscribe to events on the ones deemed important.

The remote session creates less network traffic and uses fewer system resources than the remote control applications and. v Identify updates available for your systems. and IBM Systems Director agent and server code on managed systems without an upgrade or migration of the installed product. is useful in low-bandwidth situations. such as prerequisites. v Download. Remote access manager Remote access manager provides tools that support running and monitoring applications and services running on remote systems. Virtualization manager Virtualization manager provides tools for managing the lifecycle of virtual resources. v View update history and status of targeted systems. v Create and manage event actions that identify tasks or commands to run or notifications to send. 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. Remote Desktop (RDP). which connects to the service processor of the target system. v Transfer files from one location to another and synchronizing files. device drivers. v Detect and view out-of-date 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. v Create custom event-automation plans used to automate tasks and other responses to situations that occur in your environment. 12 IBMSystems Director Systems Management Guide . v Download and review update information. therefore. content letters. v Create and manage event filters that allow the event automation plans to target specific events. distribute and install available and requisite updates tin a single request without repackaging or performing each step in the process separately. and web-based remote control for IBM BladeCenter and RSA. v Create customized update groups for your company’s certified list of updates. readmes. directories. and associated collateral. firmware and BIOS. v Get a notification when systems are in need of updates and which updates are needed. or drives using a secure alternative to FTP. v Open console windows to one or more POWER managed systems. v Run hardware management commands from the hardware command line. v Run command-line programs through a remote session. Release Notes. Update manager Update manager provides tools for maintaining current versions of operating systems. v Execute a command on one or more managed systems in parallel. including Virtual Network Computing (VNC). 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.

health and status monitoring. Overview 13 . 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. health and status monitoring. inventory. configure. VMware and Xen virtualization. You can use Network Management to: v Discover network devices in your environment. It also provides platform-specific functions. Microsoft Virtual Server. VMware. 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 configuration. v Review your network device inventory. Integrated Virtualization Manager (IVM). updates. These include Hardware Management Console (HMC). including discovery. You can use the virtualization manager plug-in to: v Work with virtualized environments and tools. As a result of this cross-solution management consolidation. and virtualization. and apply templates to configure devices. 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. v View network device configuration settings. and to access status information about them. you can visualize and control both the physical and virtual resources from a single user interface. such as relocating a virtual server based on critical hardware alerts v Create. 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. Integrated Virtualization Manager (IVM). v Monitor the health and status of network devices. Some additional basic discovery and health management is supported for z/VM virtualization. v Run network diagnostics tools like ping and traceroute. and Xen virtualization v Viewing topology that shows the connections between physical and virtual resources. Chapter 1. including Hardware Management Console (HMC). Microsoft Virtual Server. 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. configuration.Virtualization manager now includes support for virtualized environments managed by wholly different server virtualization environments. and update these virtual servers. This plug-in provides functions to discover. including discovery. monitor status.

IBM Power Systems management IBM Power Systems management provides lifecycle management of your IBM Power systems. and DS6000.1. and TotalStorage Productivity Center (TPC) to manage SAN Volume Controller (SVC). 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. and relocating virtual servers between host systems. configuration. including discovery. health and status monitoring. updates. including discovery. 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. editing virtual server resources.1 and IBM i 5. 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. It also provides platform-specific functions.com/ common/ssi/fcgi-bin/ssialias?infotype=SA&subtype=WH &appname=STGE_PO_PO_USEN&htmlfid=POW03011USEN &attachment=POW03011USEN. health and status monitoring. It also provides platform-specific functions. v Perform management tasks that are available from the IBM Systems Director Web interface for AIX 6. DS4000. and virtualization. BladeCenter SAS modules. including managing power. 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. and virtualization. 14 IBMSystems Director Systems Management Guide . creating virtual serves.ibm.PDF IBM System Storage management IBM System Storage management provides lifecycle management of your physical and virtual storage systems. updates. see the Managing IBM Power Servers with IBM Systems Director 6. and platform managers such as Hardware Management Console (HMC) and Integrated Virtualization Manager (IVM) platform managers.1 white paper on the Web at: www.4 and 6. and BC-S RAID SAS modules v Use embedded management interfaces for DS3000. configuration. For additional information about managing the virtualization and consolidation on Power systems using IBM Systems Director. IBM i.

v Create addresses for blade servers. All information sent to IBM® is stored in a secure IBM® database and used for improved problem determination. identifies and reports hardware problems and service information automatically to IBM® for service and support. v Determine power usage for all components of a rack. 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. Active Energy Manager is a for-fee licensed plug-in that supports Windows. BladeCenter Open Fabric Manager is a for-fee plug-in that supports all platforms that IBM Systems Director supports. which includes the Electronic Service Agent tool. as well as storage boot targets for up to 100 chassis or 1400 blade servers. Service and Support Manager plug-in The Service and Support Manager plug-in. see the IBM Systems Director Web site at www. You can use Active Energy Manager to: v Allocate less power and cooling infrastructure to your IBM® servers. Chapter 1. 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.com/systems/management/director/plugins/. monitor and collect energy-consumption data from IBM® systems including IBM BladeCenter chassis and rack-mounted System x servers. Overview 15 . v Communicate with IBM® using a secure Internet connection using encryption and authentication. For a complete list of available plug-ins and for information about how to download and install the plug-ins. v Lower power usage on select IBM® servers. Linux for x86. Active Energy Manager plug-in The Active Energy Manager plug-in helps you to manage. 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. v Collect and send scheduled system inventory and diagnostic inventory to an IBM® database. Service and Support Manager is a free plug-in that supports Windows and Linux for x86 platforms. v Plan for the future by viewing trends of power usage over time. This inventory information is available to IBM® support representatives when they are solving your problem.ibm. 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. save the addresses to a configuration file. You can use this plug-in to: v Pre-assign MAC and WWN addresses.

Web-Based Enterprise Management (WEBM) and Extensible Markup Language (XML). HP OpenView NNM. Microsoft Systems Center Operations Manager.boulder. you can use your enterprise-management software to manage systems that have Platform Agent or Common Agent software installed on them. or information alerts. warning. Why am I starting at the Welcome page? In IBM Director Console version 5.20. This information included the number of managed objects that had critical. and Microsoft Systems Management Server. You can use Platform Agent software to: v Gather detailed inventory information about your systems. With the IBM Systems Director UIMs and management packs. distribute IBM Systems Director software packages. the status of IBM Director. memory. and the number of managed objects in the Group Contents pane. Platform Agent uses some of the latest systems-management standards.1? You know what you need to do in IBM Director 5. now use this section to learn how to do it in IBM Systems Director 6. Meeting customer demand for a Web-based interface. and for some UIMs. 16 IBMSystems Director Systems Management Guide . IBM Systems Director UIMs and management packs provide enhancements to the enterprise-management products that you can use to collect inventory data. 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. and system monitor capabilities. Use these topics to find answers to some of the questions you might have about IBM Systems Director 6. I’m a 5. the Welcome page gives you at-a-glance status information. Tivoli Management Framework. the host and login information for IBM Director Server. and hardware.1. How do I use 6.html. limited status information was displayed along the bottom of the window. IBM Systems Director 6. You can also configure IBM Systems Director Server to forward alerts (such as SNMP) to higher-level enterprise managers.20 user.1 delivers cutting-edge usability built on industry-accepted Web-interface standards. including operating system. including CA Unicenter NSM. After you become accustomed to this interface. HP OpenView Operations for Windows.com/infocenter/systems/topic/uims/ fqs0_main.20. including Common Information Model (CIM). network adapters. event log.1. to provide compatibility with your existing enterprise-management software. view IBM Systems Director event notifications.ibm. v Track your systems with features such as power management. you’ll be able to see the status of your systems management environment quickly and more easily than ever before. see IBM Systems Director Upward Integration Modules in the IBM Systems information center on the Web at publib. For more information about upward integration modules. Tivoli Netview. In the IBM Systems Director Web interface.

Find a task Provides a way to quickly and easily find any task in IBM Systems Director. Figure 2.20 user. View updates Checks for and displays any updates that are available from the IBM® Web site that are required by IBM Systems Director Server. This information is specifically designed for IBM Director version 5. I’m a 5. 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. and access tutorials to expand your skills with IBM Systems Director. The Welcome page lets you start your work with a clear picture of your current systems-management environment. Overview 17 . The Welcome page gives you information about all of your systems with fast-path options to detailed information and tasks.0 compared to the tasks in IBM Director version 5. make sure IBM Systems Director and its plug-ins are setup and configured.1? Opens the IBM Systems Director information center to provide information that describes how to use IBM Systems Director 6. manage your environment from plug-in summary pages.20.20 users that want to understand how to complete familiar tasks using the new IBM Systems Director Web interface.1. IBM Systems Director Welcome page Use the IBM Systems Director Welcome page to complete first-time setup steps. Manage. Chapter 1. The Welcome page displaying the Start. Web resources Displays other information resources that are available on the Web. how do I use 6. About Displays the version of your IBM Systems Director installation.

request access to your discovered resources. 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. see “Security. and collect inventory from your resources. it is not displayed. Then. otherwise.” 18 IBMSystems Director Systems Management Guide . use the next steps provided on this page to make IBM Systems Director more productive. For more information. A user must have the AllPermission permission to view this page.

Chapter 1. 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.Figure 3. Overview 19 .

Optional tasks Provides optional tasks for getting started including the discovery. Next Steps Provides typical tasks for setting up IBM Systems Director. 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. Click any of these links to display detailed information about the affected systems and resources. The message associated with each plug-in changes based on whether the plug-in is ready to use. the Manage page is displayed by default when you view the Welcome page. and configuring your systems. The Manage tab includes an icon that is displayed if any problems exist with one or more plug-ins. After the initial discovery is completed. Discover Performs initial discovery in your systems-management environment. creating thresholds and event automation plans. and the number of systems on which inventory has not been collected. the Manage page is not displayed. This information includes the number of operating systems that are managed by way of the Common Agent. inventory. Note: The Manage page displays only the plug-ins that the user is authorized to use. installing Common Agent on systems. This discovery method searches the entire subnet of the server on which IBM Systems Director Server is installed. checking for updates. setting up security. It utilizes all the protocols that IBM Systems Director uses to discover systems. If a user is not authorized to use any plug-ins. including registering with IBM®. this page provides links to the applicable tasks that you must perform to complete setup or configuration of the plug-in. Platform Agent. 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. Status chart Provides status information about resources that IBM Systems Director has discovered. or no agent. the number of systems to which you do not have access. 20 IBMSystems Director Systems Management Guide . and navigate resources. If a plug-in is not ready to use.

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. Chapter 1. the Error-connecting icon is displayed on the Manage tab. the Setup-required icon is displayed on the Manage tab. Overview 21 . then no icon is displayed on the Manage tab.Figure 4. No icon If all plug-ins are in the ready state or collecting-data state . If one or more plug-ins are in the Setup-required state.

The Welcome page interface displaying the Manage page 22 IBMSystems Director Systems Management Guide .Figure 5.

Plug-in title Click the plug-in title to display the plug-in summary page. It also reports that last time the information was refreshed. Each link opens a tutorial section in the “Learning and tutorials” section of the IBM Systems Director information center. a Web site. Related concepts The Start page The Learn page The Learn page: Provides a list of available tutorial links. Chapter 1. identifying applicable types of servers required by 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. Refresh Click to refresh the ready-for-use information. The summary page provides tasks and information that you typically use in that plug-in. or other setup activities. or another destination. Collecting data The process to determine whether a plug-in is ready to use has started and might take a long time. Hover help for each link provides a description for that tutorial. enabling of firewall support. To determine when the plug-in is ready. Setup required The plug-in is not set up correctly or the set up is currently incomplete. which might be the management server. A message and additional links are displayed providing information about any required setup. Error connecting The plug-in has failed to connect to the applicable destination. such as additional configuring. Plug-in links Each plug-in section provides links that you can use to complete any configuration or setup activities. click Refresh (located at the bottom of the page) and if the plug-in is ready the status icon will change. Overview 23 .

You must have access to the Internet to view them. Otherwise. Platform Agent. If this is the first time using IBM Systems Director. Related concepts The Start page The Manage page Starting work in IBM Systems Director Before IBM Systems Director can manage your systems. 24 IBMSystems Director Systems Management Guide . see “Learning and tutorials. the systems must be discovered. the number of systems to which you do not have access. or no agent. the Welcome page is displayed automatically.” Hover help Provides a description for each tutorial. To get started with IBM Systems Director. Using the Welcome page. 2. Tip: The tutorials are launched from the Internet. you can set up IBM Systems Director for use for the first time. This section provides status information about resources that IBM Systems Director has discovered. click Welcome. On the IBM Systems Director Welcome page.Figure 6. view the Getting Started section on the Start page. For more information about e-learning and tutorials. 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. complete the following steps: 1. in the IBM Systems Director navigation area. This information includes the number of operating systems that are managed by way of the Common Agent.

installing Common Agent on systems. This section provides typical tasks for setting up IBM Systems Director. the tasks that are commonly used when setting up IBM Systems Director are provided. click Welcome. In the Optional tasks area. and configuring your systems. and the number of systems on which inventory has not been collected. checking for updates. creating thresholds and event automation plans. Overview 25 . including registering with IBM®. View the Next Steps section on the Start page. Browse the Manage page to determine the plug-ins that are in your IBM Systems Director installation and whether they are ready for use. click Refresh (located at the bottom of the page) and if the plug-in is ready the status icon will change. To determine when the plug-in is ready. 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. click the Manage tab. To determine whether plug-ins are ready for use. On the Welcome page. Note: If you have not performed discovery yet. Click any of these links to display detailed information about the affected systems and resources. discovery and system access information is reported only for the management server. Collecting data The process to determine whether a plug-in is ready to use has started and might take a long time. complete the following steps: 1. In the IBM Systems Director navigation area. 3. 2. 3. 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. setting up security. Chapter 1.

6. To view the IBM Systems Director Server summary. Error connecting The plug-in has failed to connect to the applicable destination. On the Manage page. click the Manage tab. a Web site. Complete the setup tasks listed for the plug-in. its last restart date and time. 5. or other setup activities. which might be the management server. In the IBM Systems Director navigation area. 3. 26 IBMSystems Director Systems Management Guide . click the displayed links to complete the setup and configuration. identifying applicable types of servers required by that plug-in. This section provides the following information: v The management server name. complete the following steps: 1. 4. 4. The affected plug-in is now ready to use and its status is updated. such as additional configuring. Click the name to view the properties page for the server. Note that information on this page is refreshed automatically when there are any changes. IBM Systems Director checks the plug-in. 2. The IBM Systems Director Server summary is displayed. Setup required The plug-in is not set up correctly or the set up is currently incomplete. On the Welcome page. click Refresh. If a plug-in reports that it has a problem. scroll to the IBM Systems Director Server section of the page and click the IBM Systems Director Server section heading. enabling of firewall support. A message and additional links are displayed providing information about any required setup. 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). or another destination. if applicable. View the IBM Systems Director status section. click Welcome. On the Welcome page. v The current status for IBM Systems Director Server and.

see “Finding a task. Add a role Click Add a role to create a role. v The number of roles that are defined in your IBM Systems Director Server environment. or delete roles that are used to assign access to users. Note: This link opens the IBM Systems Director information center and requires Internet access. For more information. Overview 27 . and the number of active users v In the Common tasks area. You also can reach the summary page by using Find a Task. 5. v The type of authentication used v The known ports that are in use. the following links are provided: System discovery Click System discovery to discover systems at a specific network address or range of addresses. you can run the selected task. including view and manage discovery options on an individual resource level. 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. Navigate resources Click Navigate Resources to view. Click this link to display the discovered systems. Click this link to view the Users page that displays the affected users. v In the Common tasks area. Manage Roles Click Manage Roles to create. Click this link to view the Users page that displays the defined users. View the Users and roles section. 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.” Chapter 1. v The number of systems discovered. Advanced system discovery Click Advanced system discovery to discover a specific type of resource or schedule a discovery task. Then. memory use. Find a resource Click Find a resource to quickly and easily find a particular resource. storage use. with which you can collect the most current inventory from a resource or view the inventory of a resource. Click All possible ports to view information about ports that IBM Systems Director might use. This section provides the following information: v The number of users that do not have access to any resources. and navigate among resources in your systems-management environment. edit. v The number of users that are defined in your IBM Systems Director Server environment. Click this link to view the Roles page. Find a task Click Find a task to quickly and easily find any task. Collect and view inventory Click Collect and view inventory to open the View and Collect Inventory task. work with.

v Go to the IBM Systems Director customer forum.html to review scenarios and other information resources. click the plug-in section heading to view its Summary page. click Welcome. click Related Web Resources. To view updates. click Welcome to view the Welcome page and complete any of the following steps: 28 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 “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. v On the Welcome page. see “Accessing the IBM Systems Director customer forum.com/ infocenter/systems/topic/director_6. v Go to the IBM Systems Director information center at publib. For more information.” v To familiarize yourself with other information resources available on the Web. click the Learn tab. On the Welcome page. You can learn more about IBM Systems Director in the following ways: v In the IBM Systems Director navigation area. in the IBM Systems Director navigation area. 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.1/fqm0_main.boulder. click the Manage tab.ibm. View the available tutorials to expand your skills with IBM Systems Director. For each plug-in.

– Create an update group to contain the updates for your selected systems. The Learn page is displayed with the available tutorials for the installed plug-ins. in the Next Steps section. – Run or schedule a check for updates. In the Run . 3. 2. On the Manage page. To view tutorials. click the Learn tab. 3. Overview 29 . complete the following steps: 1. Tip: The tutorials are launched from the Internet. Hover help provides a description for each tutorial. click OK to start Check for Updates immediately. For more information about e-learning and tutorials. view the Update Manager section and click Check for Updates. The View Updates page is displayed. you can start managing updates in the following ways: – Select the systems to keep in compliance with the latest updates.” Chapter 1. On the Check for Updates page. 2. Click the tutorial link for the task about which you want to learn.Check for Updates window. 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. click Check for updates on discovered systems. A message is displayed stating that the Check for Updates has run. IBM Systems Director checks for any updates that are available from the IBM® Web site. In the IBM Systems Director navigation area. – Configure a connection to the Internet. You must have access to the Internet to view them. v On the Welcome page. Click Show Updates. click View updates. The Show Updates page is displayed.v On the Welcome page. On the Welcome page. Using the Check for Updates page. v On the Start page. in the upper right-corner. 1. The Check for Updates page described in the preceding step is displayed. see “Learning and tutorials. click Welcome. select the types of updates for which you want check and click OK. click the Manage tab.

along with controls to customize the Web interface for your specific needs. 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 navigation area provides commonly used tasks at the top. the Welcome page is displayed in the content area. 30 IBMSystems Director Systems Management Guide .

Figure 7. The navigation provides links to tasks you can perform on your resources. The content area changes depending on the item you select in the navigation area. Overview 31 . this list provides the following alternate view selections: Chapter 1. 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. Health Summary. by default you see the Welcome page for IBM Systems Director in the content area. and Automation and Settings. Examples of typical tasks might include Navigate Resources.” View list In the navigation area. For more information. Inventory. You can customize aspects of the content area using the Navigation Preferences. Content area When you open the Web interface. see “Setting navigation preferences.

” IBM Systems Director Displays only IBM Systems Director tasks. Help Displays the help system. see “Customizing the Web interface. Alternatively.20 you could manually discover an individual system. For more information. This is the default view. My tasks Displays a customized list of tasks. All tasks Displays all the tasks that are available in your IBM Systems Director installation. click System discovery under Optional tasks. or use discovery preferences. 32 IBMSystems Director Systems Management Guide . The System Discovery page is displayed. In the IBM Systems Director Web interface. Performing a system discovery Use the System Discovery task to identify systems at a specific network address or range of addresses. and the default navigation area view. complete the following steps: 1. Logout Logs out of IBM Systems Director. expand Inventory and then click System Discovery. these tasks are available from the Inventory section of the navigation area. How do I discover my systems? In IBM Director Console version 5. you can perform an initial discovery of your subnet from the Start page on the Welcome page. From the Start page. To perform a system discovery.” Manage Open Pages Provides a way to manage and close one or more open pages. 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. you can also link to tasks to discover individual systems as well as create discovery profiles for advanced system discovery. Open the System Discovery page using either of these two methods: v On the Welcome page. see “Customizing the Web interface. the page that is displayed first of these automatically started pages. Close Page Closes the page that you are viewing. v In the IBM Systems Director Web interface navigation area. For more information.

select it from the Select resource type list. type the host name of the system that you want to discover. 3. Chapter 1. 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. 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. Click Single system (Hostname). For the IP address range that contains the systems that you want to discover. 2. System discovery methods To do this task: Complete these steps: Add a single IP address 1. select it from the Select resource type list. Add a range of IP addresses 1. 2. The Processing discovery protocols message is displayed and the progress of the discovery process is displayed as a spinning graphic. select it from the Select resource type list. In the IP address field. they are displayed in the Discovered Systems table. 3. Overview 33 . 3. Note: After a resource is discovered. In the Hostname field. 2. the virtual systems that are associated with that resource are also discovered. Click Discover.2. 3. click Stop during discovery. Add a host name of a system 1. Click Single system (IP address). Click Multiple systems (Range of IP addresses). If you want to discover only a specific resource type. 4. If you want to discover only a specific resource type. Optional: If you want to stop the discovery process. Select one of the following discovery methods: Table 3. type the IP address of the system that you want to discover. If you want to discover only a specific resource type. As systems are discovered.

The default system subtype is All. To create a discovery profile. click Create. expand Inventory and then click Advanced System Discovery. 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. use the System subtype list to select a subtype for the system type that you previously selected. The Protocol Selection page is displayed. 8. select the type of resource that you want to discover with the profile. 10. Click Next. Optional: If you want to provide further granularity to your discovery search. Details for each protocol are as follows: 34 IBMSystems Director Systems Management Guide . you can create a discovery profile. 9. Note: The list of system subtypes is dynamically populated based on which system type you choose. In the Profile description field. The Advanced Discovery Wizard opens and the Welcome page is displayed. From the System type list. The Profile properties page is displayed. type a brief description for the profile. Click Next. The protocols that are available on the next page of the Advanced Discovery Wizard depend on which profile type is selected here. v In the IBM Systems Director Web interface navigation area. IBM Systems Director Server uses only the communication protocols that are saved in the profile. Note: When the profile is run. clicking Next on each page to navigate to the next page. Complete all pages for each protocol that you selected. Open the Advanced System Discovery page using either of these two methods: v On the Welcome page. 6. which will discover all system subtypes for the selected system type. type a descriptive name for the profile. complete the following steps: 1. Select the protocols that you want to use for the discovery profile. 7. 5. 2. 4. clear Show this Welcome page next time. click Advanced System Discovery under Optional tasks. Optional: To prevent the Welcome page from displaying the next time you create a profile. Click Next. When a profile that contains multiple protocols is run. On the Advanced System Discovery page. the management server sends an IP packet for each protocol in the profile to every resource that is targeted. 3. In the Profile name field. 11. which increases network traffic.

only the unicast discovery is performed. if you fill in all three sections. or you can import the addresses. Selecting individual agent managers In the list of agent managers. Adding a single IP address a. and then return to fill out another section and discover those other resources. Select Add a range of IP addresses. When configuring CAS IP addresses. ensure that you configure multicast and broadcast if you choose any of those profile types. Click Add to add the IP address to the list. type the IP address of the resource that you want to discover. only one method at a time will be used to discover resources. Note: You cannot configure directory agents for the following profile types: v Hardware management console v Management controller v Server. In the Single IP address or beginning range field. d. c. or directory agents to discover your resources. multicast and broadcast. Overview 35 . Unicast b. if you want to use multiple methods to discover resources. 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. However. Chapter 1. multicast and broadcast. For example. option. you can add IP addresses either individually or as a range. b. Repeat this procedure until you have added all the IP addresses. Also activate or deactivate access request automation and activate or deactivate inventory discovery automation.Agent manager configuration Select individual agent managers or choose to use all available agent managers with your profile. Click Add to add the IP addresses to the list. Selecting all available agent managers Select the Use all available agent managers when this profile is run. Select Add a single IP address. Adding a range of IP addresses a. and directory agents) are presented on this page and you can provide information for all three at once. For the IP address range that contains the resources that you want to discover. b. Multicast and broadcast So. c. discover those resources. when discovering an IVM Therefore. you must fill out one section. select the ones that you want to use for discovery. Attention: All three discovery methods (unicast. Directory agents c. Common Agent Services (CAS) configuration Configure either unicast. The priority for discovery method processing is as follows: a.

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

Activating inventory discovery automation a. d. Common Information Model (CIM) configuration Configure either unicast. Overview 37 . ensure that you configure multicast and broadcast if you choose any of those profile types. b. or you can import the addresses. Chapter 1. type the IP address of the resource that you want to discover. Directory agents c. Unicast b. when discovering an IVM Therefore. or directory agents to discover your resources. c. Deactivating access request automation a. Select Deactivate. type the password for the user ID. b. select the profile that you want to use for automatic inventory discovery.use the following inventory profile. b. In the Single IP address or beginning range field. Multicast and broadcast So. if you want to use multiple methods to discover resources. Adding a single IP address a. For example. Activating access request automation a. you can add IP addresses either individually or as a range. In the Password field. discover those resources.use the following user login information. The priority for discovery method processing is as follows: a. Note: You cannot configure directory agents for the following profile types: v Hardware management console v Management controller v Server. type a valid user ID for the resource. and then return to fill out another section and discover those other resources. However. In the User ID field. Also activate or deactivate access request automation and activate or deactivate inventory discovery automation. Select Deactivate. if you fill in all three sections. c. multicast and broadcast. only one method at a time will be used to discover resources. Click Add to add the IP address to the list. you must fill out one section. and directory agents) are presented on this page and you can provide information for all three at once. When setting inventory discovery automation. In the Inventory profiles list. multicast and broadcast. When configuring CIM IP addresses. Attention: All three discovery methods (unicast. Select Add a single IP address. you can choose to deactivate or activate (with an associated inventory profile) the feature. Deactivating inventory discovery automation a. Repeat this procedure until you have added all the IP addresses. Select Activate . Select Activate . only the unicast discovery is performed.

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

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

However. Adding a single IP address a. b. Instead. type in the name of the import file or click Browse to search for the file. Select Activate . you will not gain access to IPC discovered resources when the automatic access request runs. c. type a valid user ID for the resource. b. Adding a range of IP addresses 40 IBMSystems Director Systems Management Guide . When configuring unicast. Select Add a single IP address. So. Note: Ensure that the file you use is a line delimited file with one IP address on each line. so these options will not be displayed if you configure only IPC. Also activate or deactivate access request automation and activate or deactivate inventory discovery automation. those options will be displayed but apply to only the supported protocols. or you can import the addresses. type the IP address of the resource that you want to discover.use the following user login information. you can choose to deactivate or activate (with the appropriate login information) the feature. Activating access request automation a. c. Select Activate . Deactivating inventory discovery automation a. Activating inventory discovery automation a. b. Select Deactivate.use the following inventory profile. Click Add to add the IP address to the list. you can add IP addresses either individually or as a range. if you configure IPC along with other protocols that support access request automation and inventory discovery automation. you can choose to deactivate or activate (with an associated inventory profile) the feature. Note: Access request automation and inventory discovery automation are not supported on IPC. Deactivating access request automation a. Select Deactivate. Repeat this procedure until you have added all the IP addresses. When setting inventory discovery automation. In the Select the file that you want to import field. even if you supply the correct credentials during configuration of access request automation. Interprocess Communication (IPC) configuration Configure either unicast or multicast and broadcast (general or directed) to discover your resources and then optionally configure broadcast relays. b. In the Inventory profiles list. for example. you need to request access and collect inventory manually using the tasks provided by IBM Systems Director. d. In the Single IP address or beginning range field. select the profile that you want to use for automatic inventory discovery. Click OK to import the IP addresses. type the password for the user ID. c. In the User ID field. In the Password field. When setting access request automation.

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

type the password for the user ID. you can choose to deactivate or activate (with an associated inventory profile) the feature. Click Add to add the IP addresses to the list. Click Add to add the IP address to the list. or directory agents to discover your resources. b. or you can import the addresses. type the IP address of the resource that you want to discover. d. c.use the following user login information. Note: Ensure that the file you use is a line delimited file with one IP address on each line. you can choose to deactivate or activate (with the appropriate login information) the feature. select the profile that you want to use for automatic inventory discovery. c. In the Single IP address or beginning range field. In the Select the file that you want to import field. 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. Repeat this procedure until you have added all the IP addresses. type a valid user ID for the resource. Deactivating inventory discovery automation a. When setting inventory discovery automation. When setting access request automation. In the User ID field. Service Location Protocol (SLP) configuration Configure either unicast. Select Deactivate. Repeat this procedure until you have added all the IP addresses. type in the name of the import file or click Browse to search for the file. Select Activate . b. Activating inventory discovery automation a. Importing IP addresses a. Deactivating access request automation a. d. When configuring ssh IP addresses. 42 IBMSystems Director Systems Management Guide . Select Import. Select Deactivate. Select Add a single IP address. b. Click OK to import the IP addresses. multicast and broadcast. b. c. In the Password field. Select Activate .use the following inventory profile. you can add IP addresses either individually or as a range. Activating access request automation a. In the Inventory profiles list. Adding a single IP address a. For the IP address range that contains the resources that you want to discover. Adding a range of IP addresses a. c. Select Add a range of IP addresses. b.

Click OK to import the IP addresses. Click Add to add the IP address to the list. Multicast and broadcast So. c. if you fill in all three sections. b. c. Repeat this procedure until you have added all the IP addresses. However. When configuring unicast. Select Add a single IP address. b. Overview 43 . only one method at a time will be used to discover resources. and directory agents) are presented on this page and you can provide information for all three at once. When configuring multicast and broadcast. Importing IP addresses a. For example. type in the name of the import file or click Browse to search for the file. In the Select the file that you want to import field. Directory agents c. you can add IP addresses either individually or as a range.Attention: All three discovery methods (unicast. The priority for discovery method processing is as follows: a. Click Add to add the IP addresses to the list. b. ensure that you configure multicast and broadcast if you choose any of those profile types. Adding a single IP address a. multicast and broadcast. if you want to use multiple methods to discover resources. only the unicast discovery is performed. For the IP address range that contains the resources that you want to discover. Unicast b. Note: Ensure that the file you use is a line delimited file with one IP address on each line. Note: You cannot configure directory agents for the following profile types: v Hardware management console v Management controller v Server. and then return to fill out another section and discover those other resources. d. type the IP address of the resource that you want to discover. In the Single IP address or beginning range field. you must fill out one section. select to enable either and set the timeout period. Select Import. discover those resources. or you can import the addresses. c. Chapter 1. Adding a range of IP addresses a. 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. Repeat this procedure until you have added all the IP addresses. d. when discovering an IVM Therefore. Select Add a range of IP addresses.

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

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

protocol. you select a hardware type. Click Edit a profile. In the Context engine ID (optional) field. In the SNMPv3 profiles list. Configuring a direct connection a. Click Apply. When configuring a direct connection. select the profile that you want to delete. Modify entries in the fields as needed. Select a discovery type at the top of the page to display options for configuring that type. and port. type the ID of the context engine. Deleting a SNMPv3 profile a. c. Note: You cannot configure directory agents for the following profile types: v Hardware management console v Management controller v Server. Editing a SNMPv3 profile a. In the Confirm privacy password field. select the profile that you want to edit. In the SNMPv3 profiles list. or a proxy using directory agents. In the Hardware type field. In the Protocol field. Click Apply to add the profile to the SNMPv3 profiles list. retype the privacy password. Also activate or deactivate access request automation and activate or deactivate inventory discovery automation. select the protocol to use to make the connection. b. ensure that you configure multicast and broadcast if you choose any of those profile types. select the type of hardware of the resource to which you want to connect. multicast and broadcast. when discovering an IVM Therefore. Storage Management Initiative Specification (SMI-S) configuration Configure either a direct connection. 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. type the name of any context engine that you want to specify. Choose from the following protocols: v https v http 46 IBMSystems Director Systems Management Guide . d. k. IP address. In the Context engine name (optional) field. i. l. Click Delete a profile. b. j.

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

3. If IBM Systems Director Server successfully contacts the resource. IBM Systems Director Server attempts to contact only the resource types that you specify by using the specific protocols defined in the discovery profile. such as copying it or editing it. 2. complete the following steps: 1. To perform an advanced system discovery. 4. Select Deactivate. click Advanced System Discovery under Optional tasks. When you are finished creating the profile. or run the profile.Advanced Systems Discovery page is displayed. select one or more discovery profiles that you want to use for discovery. 12. expand Inventory and then click Advanced System Discovery. During advanced system discovery. 13. Click Next. Note: If the discovery profile that you want to use for the advanced system discovery does not already exist. Use the Run . Advanced system discovery is helpful when you want to limit your discovery using criteria that you specify. it will appear in the table on the Advanced System Discovery page. The Summary page is displayed. click Create to start the Advanced Discovery Wizard.Advanced Systems Discovery page to set up optional functions and options of your system discovery task: 48 IBMSystems Director Systems Management Guide . If the profile that you want to use does not exist. Deactivating inventory discovery automation a. it is displayed in the appropriate groups in Navigate Resources. v In the IBM Systems Director Web interface navigation area. On the Advanced System Discovery page. Open the Advanced System Discovery page using either of these two methods: v On the Welcome page. you must reconfigure an existing profile for your use or create a new one. ensure that the discovery profile that you want to use exists. Click Run. You can then select the profile to run other management tasks. 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. Click Finish. The Run . Before performing an advanced system discovery.

The Active and Scheduled Jobs page is displayed and provides information about the job including status.20. When you clicked a group. Overview 49 . its members were displayed in the Group Contents pane. Chapter 1. you no longer use panes. 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. click OK. the discovered systems are displayed in Navigate Resources. a history. you view your groups in Navigate Resources which displays groups in resource views. Notification Use the Notification page to choose options for an email notification that you can receive as the discovery process progresses. you viewed groups in the Groups pane. progress. In the IBM Systems Director Web interface. When discovery is completed. 5. Note: Click Display Properties if you want to view the properties of the job. Options Use the Options page to specify the time to use for the system time and how to handle unavailable systems. 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. Schedule Use the Schedule page to set the discovery task to run immediately or at a specified time and date in the future. A discovery job is created and a message is displayed with buttons and information about the job.Advanced Systems Discovery page. You can also schedule the task to repeat at a specified frequency. When you are finished with the Run . a list of targets. Instead. and error logs.

although the amount of information and function varies depending on the task or plug-in. The IBM Systems Director Web interface provides a number of ways to view information about your resources as well as manage the resources. When you click on a group. and see the relationships among the resources using a topology map. Use the following example and descriptions to learn about the table view. also provide Topology Perspectives. Some tasks and plug-ins. Table view 50 IBMSystems Director Systems Management Guide . most notably Navigate Resources. The most typical ways are through tables and the properties view. You also can toggle from the map view to a resource view or relationship view. The properties view is always available for any resource by selecting the resource and clicking Actions → Properties. The default resource view is a table view. Table view The table view can display a list of the resources or tasks. you drill down to the group members which can be more groups or individual systems and their resources. Information and functions also are provided using the properties view. such as systems and their storage. Tables are the basic way that information is displayed in IBM Systems Director. When you select this feature. you can view a collection of related resources.20. 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. Most tasks and plug-ins provide information and function using tables. Figure 8.

right-click the resource and select an action.” Search the table Searches the table with the string or phrase provided. To change the number of entries that are displayed in the table. and the number selected. Toolbar Provides frequently used tasks as buttons. if you click Search. Available buttons vary. the Create Group button might not be. To move to the next page. Chapter 1. The table view displays a limited number of entries on a single page. see “Table navigation in IBM Systems Director. To perform an action on a resource in the view. all of the pages of a table are searched for the provided string. all systems in your environment that have Common Agent installed are displayed. If you specified an number that is not valid. depending on the task page. any matching strings in the currently displayed table are highlighted. For more information see “Setting navigation preferences. Page 1 of 3.” Tip: To got to a specific page. the page in the table does not change. only the rows that contain the string are displayed in the table. Overview 51 . filtered. To see the members of a group. but on other task pages. You can click any of these links to go back in the path. click the arrow button at the bottom left portion of the table. type a number in the provided entry field and press Enter. The resource view functions in the same way regardless of the resources that you have chosen to view. Table state information Provides navigation between pages of the table. Additionally. Resource area Displays the content of the resource area depending on the resources that you have chosen to view. For common table actions. The table view indicates the number of pages of data that is being displayed. the Create Group button is provided. 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.Breadcrumb path Provides a collection of links that show the navigation path to the current view. for example. In this example. The view drills down to view the group members in the table and another step is added to the breadcrumb path. It displays the count of resources or relationships currently shown. For example. change the Rows per table setting in the Navigation Preferences page. if you click Common-Agent systems in the table. When you type a string in this field. click on a group in the table.

Using the properties view. 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. or event automation plans that can affect the resource as well as dynamic troubleshooting information such as active status. Also. This view is available for all resources from the Actions menu and from the resource’s pop-up menu. Depending on the selected resource. You can access the properties view from any view by selecting a resource and clicking Actions → Properties. inventory. the properties view can provide information about any configuration settings. thresholds. and event log. Figure 9. Properties view 52 IBMSystems Director Systems Management Guide . jobs. Use the following example and descriptions to learn about the properties view. you can access troubleshooting information and other important details about a resource from anywhere in the IBM Systems Director Web interface. the properties view provides access to any tasks that can be performed on the selected resource by way of the Actions menu.

you can drill down to see relationships among your resources using Topology Perspectives. For more information. Resource area Displays the content of the resource area that varies depending on the resource that you have chosen to view. This page is displayed only if you have installed and activated the Service and Support Manager plug-in. the following additional pages can be provided depending on the resource type: General Displays the basic resource properties. see “Collecting and viewing inventory data. Select a resource or group of resources and click Actions → Topology Perspectives → Basic. or event automation plans that are associated with the resource. When viewing a collection of related resources. this area provides links to customized properties views provided by the plug-in. While the General page is always displayed by default. For more information. This page is displayed by default. and other issues. Actions Contains actions that are applicable to the resource displayed in the Properties view. Active Status Displays any problems. compliance concerns.” 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. software packages. see “Service and Support Summary. You can click any of these links to go back in the path.” Service and Support Displays whether Service and Support Manager is monitoring the resource for problems that can be reported automatically to IBM® support. see “Configuring systems. For more information. Overview 53 . The Basic selection provides a topology map that shows key resources that are related to the selected resource. thresholds.” Event Log Displays any event log data that might be associated with the resource. Chapter 1. Breadcrumb path Provides a collection of links that show the navigation path to the current view. Applied Activities Displays any jobs. Additional properties If present. For more information. see “Managing the Event Log. activations.” Inventory Displays any inventory data that might be associated with the resource. Configuration Displays any configuration settings that can be edited immediately or saved as a template for later deployment.

routers. resource view. For information about additional topology perspectives. 54 IBMSystems Director Systems Management Guide . Navigate Resources provides the basic topology perspective that is described in this section. 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 click on any displayed system icon or on any relationship line to select a resource or relationship. such as BladeCenter chassis and blade servers. you can toggle among the map view. select the resource and click Properties. You can access the map view from the resource view or relationship view by clicking Actions → Map View. You can drill down and view the relationships among these resources and other resources in your environment. or relationship view to manage your resources. You can also view and edit resource properties. Other plug-ins available for IBM Systems Director might provide additional perspectives on this menu. then right-click on that selected resource to display a list of available actions. Network Provides a topology map that shows network-specific resources that are related to the selected resource. You can access the topology map view by selecting one or more resources and then clicking Actions → Topology Perspectives → Basic. you can change to the resource view or relationship view. 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. and network cards. Use the following example and descriptions to learn about the map view. After you have entered the map view. including servers. 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.

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

Table 4. Zoom To Fit (F4) Scales the entire topology to fit into the topology viewport. all of its properties appear in the properties page within the Details palette. Support area Contains the Overview. You can click and drag within the Overview palette to reposition the topology. Toolbar buttons and menu (continued) Icon Name Description Zoom In (F3) Incrementally enlarges the total area of topology you want to view. See “Viewing properties and details” for more information. You also can use the Overview palette to easily reposition the resources and relationships that are displayed in the map. Click Hide Palette View on the navigation toolbar to close the support area. 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. repositioning. minimizing. You can either print the graphic using your Web-browser print feature or save the graphic as a local image. and Filter palettes. Print Graph Prints the entire topology. change the property. See “Navigating topology maps” for more information. click Edit to open the Edit Properties window. Details. and resizing. and click OK. 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. A Web browser window opens containing a JPEG image of the graph. 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. Click Show Palette View on the navigation toolbar to open the support area. When you select a resource or relationship in the topology. Print Viewport Prints only the current resources and relationships that are displayed in the topology viewport. A Web browser window opens containing a JPEG image of the graph. Overview palette Provides a view of the entire topology map with a rectangle surrounding the portion of the map displayed in the map viewport. Show Palette View Shows the support area that displays the palettes. Details palette Provides a way to work with the properties of your resources. You can perform mouse actions on the topology map such as scrolling. 56 IBMSystems Director Systems Management Guide . You can either print the graphic using your Web-browser print feature or save the graphic as a local image. and hiding palettes” for more information. Hide Palette View Hides the support area that displays the palettes. To change editable properties. This view might be only a portion of the overall topology. See “Reordering.

Chapter 1. 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. 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. See “Filtering the topology map” for more information. Related concepts “Resource view” “Relationship view” on page 59 Related tasks “Navigating topology maps” on page 128 “Reordering. When filtered. you can select the depth of related resources that you want to view in the topology. the affected resources and relationships are grayed out in the map. minimizing. the number selected. Table state information Displays the count of resources or relationships currently shown. Use the following example and descriptions to learn about the resource view. You can filter your selections by status and by resource type. The Filter palette also provides a Results page that displays the results of searching the map view. Using this menu. Overview 57 . and the number filtered. You can access the resource view from the map view or relationship view by clicking Actions → Resource View. Filter palette Provides a way to select the resources that you want to see in the topology map.

Using this menu. and their relationships. see “Table navigation in IBM Systems Director. Actions Opens a list of available actions.” Map View Click to change to the topology map view of the selected resource and its related resources. if you click Search. 58 IBMSystems Director Systems Management Guide . only the rows that contain the string are displayed in the table. its related resources. 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.Figure 11. all of the pages of a table are searched for the provided string. any matching strings in the currently displayed table are highlighted. Relationship View Click to change to the selected resource. You can click any of these links to go back in the path. When you type a string in this field. Resource View The currently selected view. Search the table Searches the table with the string or phrase provided. Depth Indicate the number of relationships from the root node to the object that is farthest away from that node. For common table actions. you can select the depth of related resources that you want to view in the table. Resource view Breadcrumb path Provides a collection of links that show the navigation path to the current view. Additionally. it displays the resource view of the selected resource and its related resources.

The table view indicates the number of pages of data that is being displayed. and the related resource. you must enter Topology Perspectives. It displays the count of resources or relationships currently shown. If you specified an number that is not valid. click on a group in the table. For example. The table view displays a limited number of entries on a single page. its type of relationship to another resource. For more information see “Setting navigation preferences. You can see the name of each resource. Use the following example and descriptions to learn about the relationship view. The view drills down to view the group members in the table and another step is added to the breadcrumb path. Before you can access the relationship view. You can access a relationship view from the map view by clicking Actions → Relationship View. there are two additional alternate views: the relationship view and the resource view. Page 1 of 3. To move to the next page. To perform an action on a resource in the view. Resource area The content of the resource area depends on the resources that you have chosen to view. Note: After you enter the map view. Chapter 1. Having entered the map view you can change among the three alternate views. filtered. all systems in your environment that have Common Agent installed will be displayed. and the number selected. click the arrow button at the bottom left portion of the table. Table state information Provides navigation between pages of the table. To see the members of a group. The resource view functions in the same way regardless of the resources that you have chosen to view. 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. for example. right-click the resource and select an action. To change the number of entries that are displayed in the table. type a number in the provided entry field and press Enter. Overview 59 . the page in the table does not change.” Tip: To got to a specific page. change the Rows per table setting in the Navigation Preferences page. if you click Common-Agent systems in the table.

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

IBM Systems Director provides the following tasks and features through plug-ins that are already installed or can be separately installed. including the Welcome page. 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. event logs. make sure that you specify https to indicate a secure port. 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. Note: A security alert window might be displayed before logging in. how to find resources.” v Discovery and inventory collection (see “Discovering systems and collecting inventory data”) v Configuring systems (see “Configuring systems”) v System status. 2009 75 .Chapter 2. and active status events (see “Monitoring system status and health”) v Event automation plans. and much more. and how to work with tables and topology maps that are used in these different views. This section provides information about the Web interface. 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. how to schedule tasks. For information see “Configuring Secure Sockets Layer (SSL) between IBM Systems Director and the Web browser client. 3. In addition to these fundamental tasks. how to find and start tasks. how to create and work with groups of resources. This is due to incorrect configuration of the Secure Sockets Layer (SSL) certificate. complete the following steps: 1. The default ports for the Web server are 8421 and 8422. event filters. Type the user ID and password that correspond to an authorized IBM Systems Director administrator user ID and password. If you use port 8422. For information about available plug-ins. see “Installation.” Notes: © Copyright IBM Corp. 1999. the different ways to view resources. and event actions (see “Automating tasks”) v Management and installation of updates to existing software products and firmware. health. 2. external network and storage switches. Click Log in. To log into IBM Systems Director Server.

You can access all tasks available in IBM 76 IBMSystems Director Systems Management Guide . 1. it is recommended that no more than 30 users log on to IBM Systems Director Server at one time. The interface also provides ways to customize itself as well as help information. 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. For optimal performance. If you do not actively use the IBM Systems Director Web interface for 30 minutes. you can log out. the automatic-timeout feature will log out your user ID from IBM Systems Director Server. Note: If you do not actively use the IBM Systems Director Web interface for 30 minutes. 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. and data in IBM Systems Director. in the Web interface. click Logout in the upper-right corner. To log off of IBM Systems Director Server. resources. Related tasks “Logging into IBM Systems Director Server” on page 75 Navigating the Web interface Navigating in the Web interface. the automatic-timeout feature will log out your user ID from IBM Systems Director Server. you can access tasks. 2.

Figure 13.” Chapter 2. The navigation provides links to tasks you can perform on your resources. and Automation and Settings. For more information. Examples of typical tasks might include Navigate Resources. see “Setting navigation preferences. 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. Content area When you open the Web interface. by default you see the Welcome page for IBM Systems Director in the content area. You can customize aspects of the content area using the Navigation Preferences. Health Summary. The content area changes depending on the item you select in the navigation area. You can access your resources using Navigate Resources. Systems Director and you can launch tasks in several other management tools. Inventory. Using the Web interface 77 .

This is the default view. For information see “Setting navigation preferences.” To customize the Web interface. the page that is displayed first of these automatically started pages. Note: In addition to these settings. The My Tasks feature provides a way to customize the tasks that are displayed in the navigation area. For more information.” IBM Systems Director Displays only IBM Systems Director tasks. including a setting for the default page that is displayed first among all of the automatically started pages. you can set one or more pages to open automatically when you log in to IBM Systems Director. 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. you can set the view that is displayed in the navigation area. Also. complete the following steps: 78 IBMSystems Director Systems Management Guide . and the default navigation area view. Logout Logs out of IBM Systems Director. this list provides the following alternate view selections: All tasks Displays all the tasks that are available in your IBM Systems Director installation. you can customize navigation preferences for table and topology views. For more information. see “Customizing the Web interface. 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. View list In the navigation area. Help Displays the help system.” Manage Open Pages Provides a way to manage and close one or more open pages. My tasks Displays a customized list of tasks. Close Page Closes the page that you are viewing. see “Customizing the Web interface. By saving task pages to My Startup Pages.

Using the Web interface 79 . select My Tasks from the Console navigation default view list. click My Startup Pages from the Select Action list. click Cancel. select the tasks that you want to display in the navigation area. 4. select My tasks from the View list. Also. 12. To add any other task pages that you want to start automatically. If you decide that you do not want a page to start automatically. 1. In the IBM Systems Director Web interface. To set your My tasks selections as the default navigation area view. Click Default to set the default page to display first among all of the automatically started task pages. 3. You always can change the navigation area view by using the View list. repeat steps 5 . 9. In IBM Systems Director. the saved tasks are displayed in the table. The selected tasks are displayed in the navigation area. when you have more page tabs that can be displayed in the width of the Web interface. click Edit ’My tasks’. click My Startup Pages in the IBM Systems Director navigation area. In the IBM Systems Director navigation area. In the IBM Systems Director navigation area. On the Add to My Startup Pages page. 8. 13. click Apply. click OK to save the settings and close the page. 6. click OK to save the selected page. select that task and click Remove.7. On the My Startup Pages page. 2. To close the page without saving the settings. 10. 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. Any changes take effect the next time you log in to IBM Systems Director. 5. To save the setting but not close the page. On the My Tasks page. 7. Select All Tasks to see all IBM Systems Director tasks. an arrow is displayed that you can click to view the Chapter 2. 11. open a task page that you want to start automatically when you log in to IBM Systems Director. When you are satisfied with your settings. To view your saved task pages. Click Apply.

complete any of the following steps: v In the IBM Systems Director Web interface. click the Help button on the page. click Close Page from the Select Action list. manage your environment from plug-in Summary pages. you can navigate to first-time setup steps. v When applicable. 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. To view help. click Help in the upper-right corner. v When applicable. Select Action list To manage and close open pages. click Manage Open Pages from the Select Action list that is located in the upper-right corner of the Web interface content area. Figure 14. additional tabs. v In a task page. v To close a page that you are viewing. click ? in the upper-right corner of the window or wizard. The IBM Systems Director help system opens in a new Web browser window. 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. and access tutorials to expand your skills with IBM Systems Director. On the Manage Open Pages page. click X on the page tab. you can close all pages by clicking Close All Pages. or view a selected page by clicking the page link. click the OK or Cancel buttons on the page. v To close a page. click ? in the upper-right corner of the page. v In a task window or wizard. 80 IBMSystems Director Systems Management Guide . make sure IBM Systems Director and its plug-ins are setup and configured. complete any of the following steps: v In the IBM Systems Director Web interface. close selected pages by selecting one or more pages and clicking Close Page.

Find a task Provides a way to quickly and easily find any task in IBM Systems Director. 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. manage your environment from plug-in summary pages. and access tutorials to expand your skills with IBM Systems Director. I’m a 5.1? Opens the IBM Systems Director information center to provide information that describes how to use IBM Systems Director 6.0 compared to the tasks in IBM Director version 5. The Welcome page displaying the Start. Figure 15.20 users that want to understand how to complete familiar tasks using the new IBM Systems Director Web interface. This information is specifically designed for IBM Director version 5. Using the Web interface 81 . Chapter 2. make sure IBM Systems Director and its plug-ins are setup and configured. how do I use 6. 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.20.20 user. About Displays the version of your IBM Systems Director installation. Manage.1.

Then. For more information. View updates Checks for and displays any updates that are available from the IBM® Web site that are required by IBM Systems Director Server. A user must have the AllPermission permission to view this page.” 82 IBMSystems Director Systems Management Guide . and collect inventory from your resources. see “Security. 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. use the next steps provided on this page to make IBM Systems Director more productive. request access to your discovered resources. it is not displayed. otherwise. Web resources Displays other information resources that are available on the Web.

Using the Web interface 83 . Chapter 2.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.

and navigate resources. setting up security. the Manage page is not displayed. Note: The Manage page displays only the plug-ins that the user is authorized to use. Click any of these links to display detailed information about the affected systems and resources. After the initial discovery is completed. inventory. Next Steps Provides typical tasks for setting up IBM Systems Director. It utilizes all the protocols that IBM Systems Director uses to discover systems. The Manage tab with the Information icon 84 IBMSystems Director Systems Management Guide . the Manage page is displayed by default when you view the Welcome page. If a user is not authorized to use any plug-ins. If a plug-in is not ready to use. The message associated with each plug-in changes based on whether the plug-in is ready to use. Optional tasks Provides optional tasks for getting started including the discovery. This information includes the number of operating systems that are managed by way of the Common Agent. 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 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. checking for updates. this page provides links to the applicable tasks that you must perform to complete setup or configuration of the plug-in. creating thresholds and event automation plans. and the number of systems on which inventory has not been collected. or no agent. the number of systems to which you do not have access. Status chart Provides status information about resources that IBM Systems Director has discovered. including registering with IBM®. The Manage tab includes an icon that is displayed if any problems exist with one or more plug-ins. This discovery method searches the entire subnet of the server on which IBM Systems Director Server is installed. Discover Performs initial discovery in your systems-management environment. and configuring your systems. installing Common Agent on systems. Figure 17. Platform Agent.

Chapter 2. the Error-connecting icon is displayed on the Manage tab. No icon If all plug-ins are in the ready state or collecting-data state . the Setup-required icon is displayed on the Manage tab. If one or more plug-ins are in the Setup-required state. Using the Web interface 85 . then no icon is displayed on the Manage tab.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.

Figure 18. The Welcome page interface displaying the Manage page 86 IBMSystems Director Systems Management Guide .

A message and additional links are displayed providing information about any required setup. Chapter 2. enabling of firewall support. click Refresh (located at the bottom of the page) and if the plug-in is ready the status icon will change. The summary page provides tasks and information that you typically use in that plug-in. identifying applicable types of servers required by that plug-in. Plug-in title Click the plug-in title to display the plug-in summary page. Using the Web interface 87 . 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. Setup required The plug-in is not set up correctly or the set up is currently incomplete. which might be the management server. It also reports that last time the information was refreshed. Each link opens a tutorial section in the “Learning and tutorials” section of the IBM Systems Director information center. To determine when the plug-in is ready. Related concepts The Start page The Learn page The Learn page Provides a list of available tutorial links. or another destination. Refresh Click to refresh the ready-for-use information. Collecting data The process to determine whether a plug-in is ready to use has started and might take a long time. Hover help for each link provides a description for that tutorial. a Web site. or other setup activities. Error connecting The plug-in has failed to connect to the applicable destination. Plug-in links Each plug-in section provides links that you can use to complete any configuration or setup activities. such as additional configuring.

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. The numeric values indicated by the event correspond to one of three severity levels in IBM Systems Director: critical. 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. System operation might be impacted if the problem is left uncorrected.Figure 19. or are on the verge of losing some other services. have had system down time. see “Learning and tutorials. You must have access to the Internet to view them. warning. 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. For more information about e-learning and tutorials.” Hover help Provides a description for each tutorial. 88 IBMSystems Director Systems Management Guide . Tip: The tutorials are launched from the Internet. or informational. These systems have already lost or will imminently lose data.

no action is required. you can set up IBM Systems Director for use for the first time. System operation might not be impacted and normal use of the hardware can continue. 3. in the IBM Systems Director navigation area. Otherwise. Chapter 2. and the number of systems on which inventory has not been collected. Platform Agent. 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. including registering with IBM®. Click any of these links to display detailed information about the affected systems and resources. To get started with IBM Systems Director. Using the Welcome page. creating thresholds and event automation plans. and configuring your systems. This section provides typical tasks for setting up IBM Systems Director. 2. click Welcome. This section provides status information about resources that IBM Systems Director has discovered. setting up security. discovery and system access information is reported only for the management server. the number of systems to which you do not have access. checking for updates. These systems can escalate to a Critical state if left uncorrected. the tasks that are commonly used when setting up IBM Systems Director are provided. These systems are operating normally and typically. or no agent. complete the following steps: 1. In the Optional tasks area. the Welcome page is displayed automatically. This information includes the number of operating systems that are managed by way of the Common Agent. View the Next Steps section on the Start page. On the IBM Systems Director Welcome page. installing Common Agent on systems. the systems must be discovered. If this is the first time using IBM Systems Director. Note: If you have not performed discovery yet. 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. view the Getting Started section on the Start page. 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. 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.ibm. 90 IBMSystems Director Systems Management Guide . click Welcome. For each plug-in. v Go to the IBM Systems Director information center at publib. For more information. click Welcome. click the Learn tab. click the Manage tab. 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. You can learn more about IBM Systems Director in the following ways: v In the IBM Systems Director navigation area. complete the following steps: 1.boulder. see “Accessing the IBM Systems Director customer forum.html to review scenarios and other information resources. To determine whether plug-ins are ready for use. In the IBM Systems Director navigation area. click Related Web Resources.1/fqm0_main. On the Welcome page. v Go to the IBM Systems Director customer forum. On the Welcome page.” v To familiarize yourself with other information resources available on the Web.com/ infocenter/systems/topic/director_6. 2. click the Manage tab. View the available tutorials to expand your skills with IBM Systems Director. v On the Welcome page. click the plug-in section heading to view its Summary page.

The affected plug-in is now ready to use and its status is updated. such as additional configuring. 6. enabling of firewall support. 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. IBM Systems Director checks the plug-in. which might be the management server. Using the Web interface 91 . click Refresh (located at the bottom of the page) and if the plug-in is ready the status icon will change. Collecting data The process to determine whether a plug-in is ready to use has started and might take a long time. Setup required The plug-in is not set up correctly or the set up is currently incomplete. Chapter 2. On the Manage page. a Web site. click the displayed links to complete the setup and configuration. 3. 4. Complete the setup tasks listed for the plug-in. or other setup activities. To determine when the plug-in is ready. 5. Error connecting The plug-in has failed to connect to the applicable destination. or another destination. identifying applicable types of servers required by that plug-in. A message and additional links are displayed providing information about any required setup. click Refresh. Browse the Manage page to determine the plug-ins that are in your IBM Systems Director installation and whether they are ready for use. If a plug-in reports that it has a problem. 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.

On the Check for Updates page. To view updates. you can start managing updates in the following ways: – Select the systems to keep in compliance with the latest updates. – Run or schedule a check for updates. in the upper right-corner. v On the Start page. v On the Welcome page. IBM Systems Director checks for any updates that are available from the IBM® Web site. – Create an update group to contain the updates for your selected systems. view the Update Manager section and click Check for Updates. The Check for Updates page described in the preceding step is displayed.” 92 IBMSystems Director Systems Management Guide . Tip: The tutorials are launched from the Internet. 2. 3. click the Manage tab. select the types of updates for which you want check and click OK. complete the following steps: 1. 2. in the IBM Systems Director navigation area. A message is displayed stating that the Check for Updates has run. 1. click View updates. in the Next Steps section. The Learn page is displayed with the available tutorials for the installed plug-ins. – Configure a connection to the Internet. Using the Check for Updates page. 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. 3. You must have access to the Internet to view them. In the Run . see “Learning and tutorials. click the Learn tab. For more information about e-learning and tutorials. Click Show Updates. On the Manage page. click OK to start Check for Updates immediately. click Welcome. click Check for updates on discovered systems.Check for Updates window. 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. The View Updates page is displayed. On the Welcome page. The Show Updates page is displayed. Hover help provides a description for each tutorial. To view tutorials. Click the tutorial link for the task about which you want to learn.

Click this link to display the discovered systems. Click All possible ports to view information about ports that IBM Systems Director might use. 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). click Welcome. On the Welcome page. Using the Web interface 93 . Advanced system discovery Click Advanced system discovery to discover a specific type of resource or schedule a discovery task. Note that information on this page is refreshed automatically when there are any changes. scroll to the IBM Systems Director Server section of the page and click the IBM Systems Director Server section heading. 2. v The current status for IBM Systems Director Server and. if applicable. 4. 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. Click the name to view the properties page for the server. complete the following steps: 1. v The type of authentication used v The known ports that are in use. To view the IBM Systems Director Server summary. and the number of active users v In the Common tasks area. Chapter 2. View the IBM Systems Director status section. storage use. its last restart date and time. click the Manage tab. Note: This link opens the IBM Systems Director information center and requires Internet access. On the Welcome page. the following links are provided: System discovery Click System discovery to discover systems at a specific network address or range of addresses. In the IBM Systems Director navigation area. v The number of systems discovered. The IBM Systems Director Server summary is displayed. 3. This section provides the following information: v The management server name. memory use.

This section provides the following information: v The number of users that do not have access to any resources. edit. Collect and view inventory Click Collect and view inventory to open the View and Collect Inventory task. and navigate among resources in your systems-management environment. Navigate resources Click Navigate Resources to view. Find a task Click Find a task to quickly and easily find any task. v In the Common tasks area. or delete roles that are used to assign access to users. you can run the selected task. see “Finding a task. Find a resource Click Find a resource to quickly and easily find a particular resource.” 94 IBMSystems Director Systems Management Guide . Add a role Click Add a role to create a role. Click this link to view the Roles page. View the Users and roles section. 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. 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. including view and manage discovery options on an individual resource level. work with. You also can reach the summary page by using Find a Task. 5. Click this link to view the Users page that displays the defined users. Manage Roles Click Manage Roles to create. with which you can collect the most current inventory from a resource or view the inventory of a resource. Then. For more information. v The number of roles that are defined in your IBM Systems Director Server environment.

too. the Related Resources menu item provides a list of any and all resources that are related to the currently selected resource. When you click a resource. if you click a group. which displays the members of the group. working with resources in tables. When you select this action. This section includes information about finding resources.” 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. Topology Perspectives is a powerful navigation feature. and working with resources in topology maps. the Properties page for that resource is displayed. including topology maps and Topology Perspectives. a breadcrumb path is displayed at the top of the page as a navigational signpost. As you navigate from one resource to another or drill down from a resource to its subcomponents. v When you view members of a group. For more information. can vary depending on the resource. you can click Actions → All My Linux Servers to view a submenu of appropriate actions for that group.” and “Working with topology maps. The breadcrumb path is extended each time you drill down. Using the Web interface 95 . For example. the default task. The menu also provides the following navigational actions: v When you select a resource. you can view a resource and its relationships to other resources in a graphical display. For example. If you click a resource. When you right-click a group. 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. the menu provides group-specific actions. the default navigational task occurs. Properties is provided at the bottom of the pop-up menu. These actions vary depending on the resource. When you right-click a resource. the members of that group are displayed. see “Topology Perspectives views. while viewing a member of the group called All My Linux Servers. the first navigational action provided in the pop-up menu is View Members. the available ways to view resources and resource information.” “Viewing resources in the topology perspective. Chapter 2.

If you right-click on this last link. If you navigate to a related resource. The properties view is always available for any resource by selecting the resource and clicking Actions → Properties. 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. also provide Topology Perspectives. you can view a collection of related resources. When you select this feature. Some tasks and plug-ins. Most tasks and plug-ins provide information and function using tables. This menu provides the same options as the Actions menu at this current location. The last link in the path identifies your current location in the resource navigation. most notably Navigate Resources. The most typical ways are through tables and the properties view. Information and functions also are provided using the properties view. although the amount of information and function varies depending on the task or plug-in. the breadcrumb path displays the menu associated with that group. You also can toggle from the map view to a resource view or relationship view. 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. Navigate Resources is used to describe navigating tables in general. such as systems and their storage. v When you view a resource in a topology map. the breadcrumb path displays the menu associated with the chassis. 96 IBMSystems Director Systems Management Guide . the breadcrumb path displays the menu associated with that resource. v When you view blade servers in a chassis. and see the relationships among the resources using a topology map. the breadcrumb path is updated to the current location. In this section. a menu is displayed.

Figure 20. Available buttons vary. These actions include those that are Chapter 2. Tables are the basic way that information is displayed in IBM Systems Director. In this example. Use the following example and descriptions to learn about the table view. Toolbar Provides frequently used tasks as buttons. the Create Group button might not be. Table view Breadcrumb path Provides a collection of links that show the navigation path to the current view. 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. Actions Opens a list of available actions. depending on the task page. You can click any of these links to go back in the path. Using the Web interface 97 . but on other task pages. the Create Group button is provided.

only the rows that contain the string are displayed in the table. The view drills down to view the group members in the table and another step is added to the breadcrumb path. the properties view can provide information about any configuration settings. click the arrow button at the bottom left portion of the table. type a number in the provided entry field and press Enter. It displays the count of resources or relationships currently shown. Additionally. or event automation plans that can affect the resource as well as dynamic troubleshooting information such as 98 IBMSystems Director Systems Management Guide . change the Rows per table setting in the Navigation Preferences page. The resource view functions in the same way regardless of the resources that you have chosen to view.” Tip: To got to a specific page. provided in the toolbar and elsewhere on the page as well as actions that are common to all tables. When you type a string in this field. you can access troubleshooting information and other important details about a resource from anywhere in the IBM Systems Director Web interface. For common table actions. The table view indicates the number of pages of data that is being displayed. for example. To move to the next page. and the number selected. all systems in your environment that have Common Agent installed are displayed. if you click Search. 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. The table view displays a limited number of entries on a single page. click on a group in the table. thresholds. right-click the resource and select an action. This view is available for all resources from the Actions menu and from the resource’s pop-up menu. jobs. For more information see “Setting navigation preferences. filtered. see “Table navigation in IBM Systems Director. Using the properties view. For example. Resource area Displays the content of the resource area depending on the resources that you have chosen to view. Table state information Provides navigation between pages of the table. the page in the table does not change. To perform an action on a resource in the view.” Search the table Searches the table with the string or phrase provided. To change the number of entries that are displayed in the table. any matching strings in the currently displayed table are highlighted. all of the pages of a table are searched for the provided string. Page 1 of 3. If you specified an number that is not valid. To see the members of a group. Depending on the selected resource. if you click Common-Agent systems in the table.

the properties view provides access to any tasks that can be performed on the selected resource by way of the Actions menu. 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. Using the Web interface 99 . Figure 21. and event log. 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. this area provides links to customized properties views provided by the plug-in. Additional properties If present. Also. the following additional pages can be provided depending on the resource type: Chapter 2. Properties view Breadcrumb path Provides a collection of links that show the navigation path to the current view. You can access the properties view from any view by selecting a resource and clicking Actions → Properties. active status. inventory. Use the following example and descriptions to learn about the properties view.

When viewing a collection of related resources. see the following topics: v “Storage topology views” 100 IBMSystems Director Systems Management Guide . or relationship view to manage your resources. Active Status Displays any problems. such as BladeCenter chassis and blade servers. This page is displayed only if you have installed and activated the Service and Support Manager plug-in.” Inventory Displays any inventory data that might be associated with the resource. see “Service and Support Summary. you can drill down to see relationships among your resources using Topology Perspectives. For more information. The Basic selection provides a topology map that shows key resources that are related to the selected resource.” Service and Support Displays whether Service and Support Manager is monitoring the resource for problems that can be reported automatically to IBM® support. Network Provides a topology map that shows network-specific resources that are related to the selected resource.” Event Log Displays any event log data that might be associated with the resource.” 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. For information about additional topology perspectives. including servers. routers. Configuration Displays any configuration settings that can be edited immediately or saved as a template for later deployment. For more information. or event automation plans that are associated with the resource. see “Collecting and viewing inventory data. see “Configuring systems. software packages. resource view. Select a resource or group of resources and click Actions → Topology Perspectives → Basic. General Displays the basic resource properties. 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. compliance concerns. activations. and other issues. thresholds. Navigate Resources provides the basic topology perspective that is described in this section. and network cards. Other plug-ins available for IBM Systems Director might provide additional perspectives on this menu. For more information. Applied Activities Displays any jobs. see “Managing the Event Log. For more information. you can toggle among the map view. This page is displayed by default.

v “The update topology perspective” v “Viewing resources in virtualization perspectives” Note: The properties view is always available for any resource. 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. Use the following example and descriptions to learn about the map view. Chapter 2. You can click on any displayed system icon or on any relationship line to select a resource or relationship. select the resource and click Properties. then right-click on that selected resource to display a list of available actions. You can also view and edit resource properties. you can change to the resource view or relationship view. You can drill down and view the relationships among these resources and other resources in your environment. After you have entered the map view. You can access the map view from the resource view or relationship view by clicking Actions → Map View. Using the Web interface 101 . You can access the topology map view by selecting one or more resources and then clicking Actions → Topology Perspectives → Basic.

Zoom Out (F2) Incrementally reduces the total area of the topology you want to view. Map view Breadcrumb path Provides a collection of links that show the navigation path to the current view. as well as pop-up menu items for resources currently selected in the topology. Select Selects resources in the topology. 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. Zoom Area Selects the part of the topology that you want to increase or decrease in size. click Actions → Properties. Search the map Searches the map for resources that have a name containing the word or phrase provided. to display the properties of the currently selected resource. Pan Provides a way for you to drag the topology map to reposition it in the topology viewport. For example. 102 IBMSystems Director Systems Management Guide . Hover Help Displays detailed information about a resource or relationship line when a mouse hovers over it.Figure 22. You can click any of these links to go back in the path.

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

Related concepts “Resource view” on page 57 “Relationship view” on page 59 Related tasks “Navigating topology maps” on page 128 “Reordering. See “Filtering the topology map” for more information. The Filter palette also provides a Results page that displays the results of searching the map view. Using this menu. Table state information Displays the count of resources or relationships currently shown. When filtered. Filter palette Provides a way to select the resources that you want to see in the topology map. 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 select the depth of related resources that you want to view in the topology. 104 IBMSystems Director Systems Management Guide . 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. the affected resources and relationships are grayed out in the map. the number selected. 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. You can filter your selections by status and by resource type. and the number filtered. minimizing.

its related resources. all of the pages of a table are searched for the provided string. and their relationships. Resource view Breadcrumb path Provides a collection of links that show the navigation path to the current view. 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. it displays the resource view of the selected resource and its related resources. Resource View The currently selected view. When you type a string in this field. Using this menu. You can click any of these links to go back in the path. Chapter 2. Relationship View Click to change to the selected resource. you can select the depth of related resources that you want to view in the table. Using the Web interface 105 . any matching strings in the currently displayed table are highlighted.Figure 23. Search the table Searches the table with the string or phrase provided. only the rows that contain the string are displayed in the table. if you click Search. For common table actions. Depth Indicate the number of relationships from the root node to the object that is farthest away from that node. Additionally. 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.

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. For more information see “Setting navigation preferences. click the arrow button at the bottom left portion of the table. You can see the name of each resource. To see the members of a group. Having entered the map view you can change among the three alternate views. Table state information Provides navigation between pages of the table. Resource area The content of the resource area depends on the resources that you have chosen to view. Use the following example and descriptions to learn about the relationship view. the page in the table does not change. you must enter Topology Perspectives. Note: After you enter the map view. right-click the resource and select an action. and the number selected. if you click Common-Agent systems in the table. there are two additional alternate views: the relationship view and the resource view. all systems in your environment that have Common Agent installed will be displayed. filtered. For example. If you specified an number that is not valid. change the Rows per table setting in the Navigation Preferences page. and the related resource. Page 1 of 3. To move to the next page. To change the number of entries that are displayed in the table. The table view displays a limited number of entries on a single page. click on a group in the table. 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.” Tip: To got to a specific page. its type of relationship to another resource. for example. Before you can access the relationship view. The table view indicates the number of pages of data that is being displayed. 106 IBMSystems Director Systems Management Guide . You can access a relationship view from the map view by clicking Actions → Relationship View. It displays the count of resources or relationships currently shown. type a number in the provided entry field and press Enter. The view drills down to view the group members in the table and another step is added to the breadcrumb path.

its related resources. Depth Indicate the number of relationships from the root node to the object that is farthest away from that node.” Map View Click to change to the topology map view of the selected resource and its related resources. it displays the selected resource. 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. Resource View Click to change to the resource view of the selected resource and its related resources. and their relationships. Search the table Searches the table with the string or phrase provided. You can click any of these links to go back in the path. Relationship View The currently selected view. For common table actions. Actions Contains actions for the selected resource and its related resources in a relationship view. any matching strings in the currently displayed table Chapter 2. Using the Web interface 107 . Relationship view Breadcrumb path Provides a collection of links that show the navigation path to the current view. Opens a list of available actions. you can select the depth of related resources that you want to view in the table. Using this menu.Figure 24. see “Table navigation in IBM Systems Director. When you type a string in this field.

To locate resources quickly. click Find a Resource. complete the following steps: 1. Note: Find a Resource is also available on the Welcome page. Select an action for the resource you want to affect. For more information see “Setting navigation preferences. Additionally. only the rows that contain the string are displayed in the table. For example. the relationships that pertain to your virtual systems and hosts will be displayed in the relationship view. The relationship view functions in the same way regardless of the types of relationships you have chosen to view. filtered. Table state information Provides navigation between pages of the table. In the IBM Systems Director Web interface navigation area. change the Rows per table setting in the Navigation Preferences page. 108 IBMSystems Director Systems Management Guide . The action you select is performed on the selected resource within the relationship. The pop-up menu provides a submenu for each resource in the relationship. if you click Virtual Servers and Hosts. To perform an action on the resources in the relationship view. all of the pages of a table are searched for the provided string. If you specified an number that is not valid. and the number selected. type a number in the provided entry field and press Enter. While you can expand and navigate through groups in Navigate Resources or within other task tables to find a particular resource. To change the number of entries that are displayed in the table. Relationship area The content of the relationship area depends on the resources that you have chosen to view. 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.” Tip: To got to a specific page. To move to the next page. for example. It displays the count of resources or relationships currently shown. are highlighted. The table view indicates the number of pages of data that is being displayed. right-click the resource name in a row. you also can quickly and easily find a particular resource using Find a Resource. The table view displays a limited number of entries on a single page. if you click Search. Page 1 of 3. A relationship between two resources is displayed in each row. click the arrow button at the bottom left portion of the table. the page in the table does not change.

Note: Do not confuse the resource view and relationship view with the navigation tables that are used throughout the IBM Systems Director Web interface. Optional: To view all the search results. If there are more than 10 results. the Topology Perspectives action is available from the Actions menu. type the name of the system and click Find. The first 10 results of the search are displayed below the field. A table is displayed with the search results. More is displayed. After you enter the topology map view. If a task provides topology perspectives. In the Find a Resource field. 3. you can view a collection of resources and see their relationships among each other in multiple ways. 4. Optional: If there are more than 10 results. 2. you can refine the search results. These views display only the resources and relationships that you selected to display in the topology perspective. Using the Web interface 109 . Chapter 2. 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. These views provide alternate ways to view the resources and relationships that are displayed in the map view. you can access the resource view and the relationship view. click More.

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

Using the Web interface 111 . v You can run some tasks on multiple resources simultaneously. select the resources. Tips: v You also can right-click the resource and select a task from the pop-up menu. Chapter 2. To perform an action on multiple resources. see “Filtering the topology map. click a resource in the list to drill down and see more resources and their relationships.” 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. click Action and click a task. select one or more resources. If you want to perform tasks or other actions on your resources. click Actions → Resource View. To view and use the resource view. 2. In the table view. 3. right-click on one of the selected resources. Results page that displays the results of searching the map view. and select a task from the pop-up menu. then. In a topology map or relationship table. complete the following steps: 1. For more information.

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

its RAID controller. After you enter the topology map view. if you choose to view three levels. v In the relationship view. Also. When selecting a view. Using the Web interface 113 .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 view the types of relationships that exist between the resources in the map view. and any attached RAID physical drives. For example. you can change to alternate views of the resources and relationships that you chose to view in the topology map view. Select a resource and then click Actions → Properties. but in a table that is easier to filter and sort. you can change to the relationship view or the resource view and then return to the map view. including their status information. v In the properties view. such as a server. the map displays all resources that are up to three levels away from the primary resource. v In the resource view. Also. If a task provides the topology map view. you can view related resources of multiple types. you can view all the troubleshooting information for a resource in one place. consider the following information: v In the map view. you can control the levels of resources that you view. the properties view is always available from the Actions menu. the Topology Perspectives action is available in the Actions menu. You first must enter the topology map view before you can change to the relationship table or resource table views. you can view all the resources from the map view. All views are available in the Actions menu and the view that you are currently using is checked. Chapter 2.

the topology view is the default view. therefore. search. you can customize your table navigation preferences and adjust table columns. the setting affects only the view that is shown when the resource is opened. 114 IBMSystems Director Systems Management Guide . You can add resources to your Favorites view that you use frequently. To set the default resource view. By default. To close the page without saving the settings. When this setting is selected. click Cancel. To reset the settings to the system-defined values. 3. sort. 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. expand Settings and click Navigation Preferences. In the IBM Systems Director Web interface navigation area. Also. select or clear Use the resource table view as the default view for topology maps. click Restore Defaults. This setting is provided for accessibility requirements and screen reader support. click Apply. 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. After you have opened the resource. To save the setting but not close the page. On the Navigation Preferences page. you can filter. you can switch to a different view. the topology view is not initially displayed when you select Topology Perspectives. When you are satisfied with your settings. complete the following steps: 1. this option is not selected. export. and print table information. click OK to save the settings and close the page. 2. In addition to navigating tables. You still must click OK or Apply to save the restored settings.

software packages. you can drill down to view disks related to a server or fans related to a BladeCenter chassis. or event automation plans that are associated with the resource. Most resources and information are displayed in tables. 3. Click a resource or group in the task table. you can access information such as inventory and event status. For example. the following information is displayed: v If you click an individual resource that contain other resources. change the Rows per table setting in the Navigation Preferences page. that uses tables for navigating resources. v If you click a resource that does not contain other resources. 2. For more information see “Setting table-navigation preferences. As you drill down through related resources or to properties pages. If you want to navigate to an earlier part of your path in the table. its subsystems or related resources are displayed. click the applicable part of the breadcrumb path located above the table. Clicking Actions → Related Resources provides a list of resources that are related to your selected resource. If you want to change the number of rows that are displayed in the table. Continue to click or drill down through resources to see lower-level subsystems or resources. Depending on the resource. The Actions menu also provides alternative ways to navigate the resources in the table. Select a related resource from the list to Chapter 2. a list of the included systems and resources is displayed. To navigate in tables. configuration settings. For information about the Properties page. complete the following steps: 1. and information about the jobs. there might be several levels through which you can drill down. 5. Depending on the pages provided for the resource. Using the Web interface 115 .” 4. Open a task. the breadcrumb path is extended to reflect the path you have taken. activations.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. You can continue to click or drill down on resources to see lower-level subsystems or resources. see “Viewing properties. thresholds.” v If you click a group. such as Navigate Resources. then that resource’s properties are displayed. Depending on the resource or group that you click.

v Globally available tasks and actions. For information about Topology Perspectives. alternate views also might be available. sorting.” v Specific tasks or actions that are applicable to a selected resource in the table. select one or more resources. navigate quickly to it. For example. Then. 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. exporting. 116 IBMSystems Director Systems Management Guide . and others. Using this list. If you want to perform tasks or other actions on your resources. If applicable. For example. you can navigate quickly to any related resource. the Topology Perspectives view displays a map of resources and their relationships starting from the selected resource. For example. you can either right-click the resource or click the Actions menu. Related Resources provides a list of resources that are related to the selected resource. see “Topology Perspectives views. Access Control. Encryption Key Reset. alternate views might be available from the Actions menu. v Actions that are specific to tables such as filtering. see “Topology Perspectives views. Power On. these tasks might include Create and Create Like if they are applicable to a resource. if you select a system in a table. and adjusting columns. If applicable. these actions might include Create Group.” 6. Clicking Actions → Topology Perspectives displays a map of resources and their relationships starting from the selected resource. For information about Topology Perspectives.

On the Properties page. complete the following steps: 1.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. Chapter 2. see “Viewing properties and details. In the table. For information about editing properties. you can access troubleshooting information and other important details about a resource from anywhere in the IBM Systems Director Web interface. and information about the jobs. select a resource. For information about viewing properties in a topology map view. Click Actions → Properties.” To view properties for a resource in a table. you can access information such as inventory and event status. activations. The number of pages and the types of information they include vary depending on the resource. 2. Using the properties view. This view is available for all resources from the Actions menu and from the resource’s pop-up menu. Some properties are editable. Using the Web interface 117 . Optional: If additional pages are available. Depending on the pages provided for the resource. View the properties displayed on the General page. thresholds. configuration settings. click them to view additional properties information and troubleshooting information. 3. see “Editing properties. software packages. or event automation plans that are associated with the resource. the resource area displays one or more pages.” 4. The General page is displayed by default.

as well as an option to match the case: v Contains v Starts with v Ends with Type information. To filter information in any table. then those types are available as filter selections. The conditions available vary depending on the type of information that the column contains: Textual information. Note: Filtering is not persistent. and storage systems. you can see the rows that match your filter criteria in the table. platform managers. filter settings are not remembered for subsequent uses of the list. Click Filter to open the selectable filtering criteria for a column. 3. physical processors. Note: The available filter conditions vary depending on the column. An additional row at the top of each column is displayed. This row contains Filter links. complete the following steps: 1. 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. for example. select the condition on which you want to filter the column. However. only servers. you can use the filtering options that are available from the Action button. if the column contains only one type. if the column contains hosts. In the Filter window. After you have completed filtering resources in the table view. Click Actions → Show Filter Row. For example. such as resource type The types present in this column determine the settings available for filtering. then filtering is disabled for that column. such as name and description The Filter window provides the following settings. 118 IBMSystems Director Systems Management Guide . 2.

If you want to clear all of your filter settings. click Actions → Clear All Filters. or date and time information The Filter window provides settings that are applicable to the specific information reported in the column. Optional: To refine your filtering. 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 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. 5. 4. When you finish filtering your table information. Health and compliance information The Filter window provides settings that are applicable to the specific information reported in the column. 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. Numeric information The Filter window provides the following settings when applicable. click Actions → Hide Filter Row. click OK. 6. 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. Chapter 2. When you are satisfied with your filter settings. time. For example. For example. you can edit the filter settings for additional columns. Using the Web interface 119 .

4. click the arrow in the Name column for the sort direction that you want. 3. to descending order (A-Z). 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 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). If you want to sort all the rows by the values in one column. click Actions → Clear All Sorts. that is. within type. v The second click reverses the sort. you can click the Up Arrow and the Down Arrow in the applicable column heading. In the First Sort list. you can use the sorting options that are available in the table column headers and from the Action menu. Optional: If you want to sort the table information on additional columns. Also. For example. select the order of the sort: Ascending (Z-A) or Descending (A-Z). select the column that contains the data you want sorted first. For example. v The third click removes the sort altogether. If you want to all the rows by the values of more than one column. When you are satisfied with your sort settings. If you want to sort the rows by type. you might want to sort all the rows by type but. In the Edit Sorts window. 2. click the arrow in the Type column. a list is displayed for each available column on which you can sort. click Actions → Edit Sort. 5. you want the rows sorted by name. 120 IBMSystems Director Systems Management Guide . click OK. continue to make selections in the additional sort lists. complete the following steps: 1. To sort information in any table. 6. if you want to sort the rows by name. If you want to clear all of your sort 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 “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. 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. complete the following steps: 1. to print tables that are more than one page long. 2. Any matching strings in the currently displayed table are highlighted. you can export the table data to a CSV file that you can subsequently import into a spreadsheet program and print using that program. To search any table. you can use your Web browser to print the table information. Click Search. Using the Web interface 121 . you can search for a specific string in the table information. Type a string in the Search the table field. Otherwise. you can view the entire table on the page). Chapter 2.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.

Tip: You can print a multiple-page table using a CSV file. 4. this is a printer setting and must be changed in the printer properties. click the option to print the selected frame. 3. 2. Typically. 3. click OK. Click Actions → Export. see “Exporting table information. Import the CSV file into a spreadsheet program and use the program’s print feature. complete the following steps: 1. Optional: Adjust your orientation setting to landscape so that the table width can be printed. 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. In the Print window. 122 IBMSystems Director Systems Management Guide .” To print a one-page table. In the file download window for your Web browser. The data is exported and a CSV file is saved in the location that you provided. Selecting this option will print only the IBM Systems Director Web interface content area and not the navigation area. If you want to increase the number of table rows that are displayed on one page. provide it and click Save. see “Setting table-navigation preferences” for information. In the Print window for your Web browser. click Save to Disk and then click OK. 2. you can export the table data to a CSV file that you can subsequently import into a spreadsheet program. In your Web browser. To export data from any IBM Systems Director Web interface table. complete the following steps: 1. click File → Print. 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 your Web browser requires a location selection. To print a multiple-page 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 “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.

userid. complete the following steps: 1. Right-click the resource (or a selected resource) and then click Add to → Favorites. is displayed in the Health Summary page. where userid is your user ID. Using the Web interface 123 . To add a resource to your Favorites. You can add a resource to your Favorites from many places in the IBM Systems Director Web interface. you can add the resource to your Favorites. expand System Status and Health and click Health Summary. To view your Favorites. Optional: If you want to add multiple resources to your Favorites at once. A confirmation message is displayed. navigate to the Health Summary page. In an IBM Systems Director Web interface table. 3. 2. navigate to the resource that you want to save. In the IBM Systems Director Web interface navigation area. Whenever the Actions menu or a pop-up menu provides the Add to → Favorites selection. select each resource in the table that you want to save. Chapter 2. Having all these resources in one location makes managing your system-management environment easier. Favorites .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.

a thumbnail of the group contents is displayed.” To add a resource to the Health Summary. The resources must be in a group. In the IBM Systems Director navigation area. navigate to the Health Summary page. 124 IBMSystems Director Systems Management Guide . For information. use the Create Group wizard to create a group. A confirmation message is displayed. complete the following steps: 1. In a table. If the resources are not in an appropriate group. see “Managing groups. Click Actions → Add to → Health Summary. 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. select the group that you want to save in the Health Summary. On the Health Summary page. To view the Health Summary. 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. expand System Status and Health and click Health Summary. The resources must be in a group. 2.

Using the Web interface 125 . This setting affects only the view that is shown when the resource is opened. or a user starts a page refresh.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. your preferred navigation view. After you have opened the resource. The default number of rows is 15. To set the preferences. complete the following steps: 1. By default. 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 option is not selected. 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. expand Settings and click Navigation Preferences. a table completes a sort. 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. you can switch to a different view. 2. By default this option is not selected. and more. a user selection that displays additional controls or options. 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. On the Navigation Preferences page. such as fixed column width. Rows per embedded table Specify the number of rows to display in an embedded table in the Chapter 2. In the IBM Systems Director Web interface navigation area. Examples of situations that can cause a notification sound include a page refreshing dynamic data. the topology view is the default view. These preferences include table accessibility.

3. Note: You cannot adjust the Name column. To adjust the order in which the columns are displayed. Click the Width tab. which is always the first column). To reset the settings to the system-defined values. click Actions → Columns. and the width for each column. The Width page provides an adjustable width setting (in pixels) for each column displayed in the table. complete the following steps: 1. To set the table-column preferences. The preferences are saved specifically for your use. You still must click OK or Apply to save the restored settings. click Restore Defaults. Note: These settings affect tables in the following ways: v If you are viewing a group when you open the Column Preferences window. Use the Add and Remove buttons to move columns between the Available columns list and the Selected columns list. These preferences include the available columns that are displayed in the table. group column preferences for other users are not affected. click OK to save the settings and close the page. how the columns are ordered (except for Name. table view for Health Summary and other navigation tables in IBM Systems Director. click Cancel. The default number of rows is 10. the preferences are saved for any time you view that same resource type. 2. select the column from the Selected columns list and use Up and Down to adjust the order. click Apply. 4. To save the setting but not close the page. In the IBM Systems Director Web interface task 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 “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. 3. select the columns that you want to display. To close the page without saving the settings. it is always the first column. When you are satisfied with your settings. In the Columns window on the Order page. the preferences are saved with the group. Note that you also can adjust the column width by dragging the column handles in the table-column header. v If you are viewing a set of resources of the same type when you open the Column Preferences window. 126 IBMSystems Director Systems Management Guide .

To close the page without saving the settings. click Apply. you can customize your topology map palettes and map preferences. click Restore Defaults. Note: You also can adjust column width by dragging the column handles in the table-column header. 6. click Restore Defaults. search. 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. The table is adjusted to display using the new column settings. export. To save the setting but not close the page. Also. You still must click OK or Apply to save the restored settings. Using the Web interface 127 . you can filter. click Cancel. and print topology maps. When you are satisfied with your settings. In addition to navigating maps. click OK to save the settings and close the page. If you want to change the settings on the page to the system-defined default values. Chapter 2. 5. To reset the settings to the system-defined values.

Click Actions → Topology Perspectives → Basic. complete the following steps: 1. Mouse actions in the topology map Interaction Description Scrolling and Topologies are often much larger than the topology-map viewing area. Click and drag to move the blue rectangle around the topology thumbnail. and diagonally in small increments. You can reposition the topology map in the following ways: v Use the eight scroll controls to scroll in eight directions. 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. you might repositioning want to reposition the map to see specific resources. the topology is repositioned in the topology map. v Press the Ctrl and arrow keys on the keyboard to scroll in four directions. A blue rectangle indicates the viewable area of the topology map. 2. To navigate in topology maps. Therefore. vertically. The topology map displays scalable topology graphs that you can manipulate using the following mouse actions: Table 7. Navigate Resources is one of these tasks. v Go to the Overview palette to reposition the topology map. When the Overview rectangle is moved. The scroll controls are displayed as white arrows on all four sides and all four corners of the topology map. 128 IBMSystems Director Systems Management Guide . navigate to a resource that you want to view in a topology map and select it. Click the arrows to move the topology horizontally. 3. The selected resource will be the root node in the topology map. then click and drag inside the topology map. Open a task that provides the topology map view as an alternate view. On the task page. v Click the Pan toolbar icon to load the mouse with the Pan cursor.

click the applicable part of the breadcrumb path located above the map. for the topology Perform an action on Right-click the icon to access the pop-up menu and then select a menu action. then select a menu action. If applicable. Chapter 2. 5. you can either right-click on the resource or click the Actions menu. Then. select the deselect action from the Actions menu. Deselect resources Click the resource again. For example. 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. Relationship View displays a table of a selected resource and its related resources. For large topology maps. and lists their relationships. Power On. click the first relationships. 6. Select multiple To select two or more relationships at the same time. Both menus provide tasks and actions that are available for the selected resources. Access Control and Encryption Key Reset. select one or more resources. Using the Web interface 129 . zoom. Alternatively. Select multiple To select two or more resources at the same time. and right-click any of the selected resources to access the pop-up multiple resources menu. if you select a system in a map. For example. You can click and drag within the Overview palette to reposition the topology. these actions might include Create Group. Note: Resizing the topology map causes the entire page to resize within the interface. If you want to navigate to an earlier part of your path. Optional: If you want to perform tasks or other actions on your resources. v Actions specific to maps such as graph mode.Table 7. Perform an action on Select multiple resources. Select a resource Click the resource icon or a resource label. Open a pop-up menu Right-click the background within the topology map. For example. These tasks and actions fall into three categories: v Specific tasks or actions that are applicable to a selected resources in the map. Then. or click on the background within the topology map. click the first resource. select the icon or label and then select an action from the Actions menu. a resource select the icon or label and then select an action from the Actions menu. v Globally available tasks and actions. for a resource Note: The pop-up menu items that are displayed are based on the icon or label that is selected. alternate views might be available. hold relationships the Ctrl key down using the mouse to select as many relationships as you want. Dragging the small gray triangle only resizes the size of the viewable area. Alternatively. Deselect a Click the relationship line again. it does not resize the topology. or click on the background within the topology map. relationship Open a pop-up menu Right-click the icon or label. these task might include Create and Create Like if they are applicable to a resource. 4. Mouse actions in the topology map (continued) Interaction Description Resizing A resizing function is provided to enlarge the topology map. and layout. 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. Select a relationship Click the relationship line. Alternatively. Then press the Ctrl resources key while using the mouse to select as many resources as you want.

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

view the Details palette. move the mouse pointer over the relationship line to view information about the relationship. You can determine the type of relationship that a line indicates in any of the following ways: v In the topology map. click the Hover Help icon . Then. see “Topology-relationship descriptions. Then. 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. The relationship type is listed in the Details palette. right-click a resource at either end of the relationship line and then click Relationship View. v In the topology map.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. For information about each relationship type. v On the topology map toolbar. A line can indicate one of many relationship types.” Chapter 2. The relationship table view is displayed. click a relationship line. There are several ways that you can determine the type that a line indicates. Using the Web interface 131 . The information is listed in the Relationship Type column. including the relationship type. minimizing.

On the Filter page. complete the following steps: 1. any resources that are a server resource type are grayed out in the topology map. go to the Resource Types group and clear the selections that you want to filter from the 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. For example. 2. the palette provides two types of settings on which you can filter: status and resource type. Note: Filtering is not persistent. filter settings are not remembered for subsequent uses of the map. For example. The palette has two pages: Filter and Results. Click the Results tab. The Results page displays a table of information about the resources that are not grayed out in the topology. 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. Any resource in the topology map that has a status matching a cleared selection is grayed out in the topology map. You can filter your selections by status and by resource type. any resources that have a status of OK are grayed out in the topology map. To filter a map. If you want to filter by resource status. if you clear the Server check box. View the Filter palette in the Support area. go to the Status Items group and clear the selections that you want to filter from the topology map. 132 IBMSystems Director Systems Management Guide . The Filter palette also provides a Results page that displays the results of searching the map view. the affected resources and relationships are grayed out in the map. 3. 4. if you clear the OK check box. If you want to filter by resource type. 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. minimizing. When filtered. Any resource of a type that matches a cleared selection is grayed out in the topology map.

minimizing. 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. The search results also are displayed in the Filter palette on its Results page. To search a map. Using the Web interface 133 . Click Search. Chapter 2. The name field is searched for the specified string. Type a string in the Search the map field. complete the following steps: 1. 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. 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. 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.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. 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. 2. minimizing.

You can either print the graphic using your Web browser print feature or save the graphic as a local image. complete the following steps in a topology map view: 1. To export data for an entire topology map. The currently displayed resources and relationships might be only a portion of the overall topology. 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. click the Print Viewport icon from the toolbar. provide it and click Save. 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. 4. complete the following steps in the topology map view: 1. A Web browser window opens containing a JPEG image of the graph. To print only the current resources and relationships that are displayed in the topology map view. The data is exported and a CSV file is saved in the location that you provided. 3. click Save to Disk and then click OK. A Web browser window opens containing a JPEG image of the graph. 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. 2. If your Web browser requires a location selection. Click Actions → Export. To print a topology map. To print the entire topology. click the Print Graph icon from the toolbar. 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. 2. 3. 134 IBMSystems Director Systems Management Guide . In the file download window for your Web browser. minimizing.

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

you can show the palettes again by clicking the Show Palette View icon on the navigation toolbar. This option is selected by default. Details. If you deselect this setting. Examples of situations that can cause a notification sound include a page refreshing dynamic data. 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. Remember palette state Select to make sure that the state of your palettes persists even as you navigate away from the topology map view. This option is selected by default. 136 IBMSystems Director Systems Management Guide . expand Settings and click Navigation Preferences. 2. and more. By default this option is not selected. and Filter palettes. These preferences include the way that topology map palettes are displayed. you maintain the customized view of your palettes even after you log out of the IBM Systems Director Web interface. To set the preferences. Details. a table completes a sort. and Filter palettes in the topology map view. or log off from the IBM Systems Director Web interface. On the Navigation Preferences page. the default topology and table sizes. By selecting Remember palette state. complete the following steps: 1. you can set the following preferences that affect the topology map view: Show palettes on initial view Select to display the Overview. a user selection that displays additional controls or options. you can customize the topology map view by minimizing or reordering the Overview. your preferred navigation view. change to another page in the overall IBM Systems Director Web interface. or a user starts a page refresh. For example. In the IBM Systems Director Web interface navigation area. you will see the topology map without the palettes. 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.

After you have opened the resource. click OK to save the settings and close the page. and the direction of the relationship is shown by the direction of the arrow attached to each line. When you are satisfied with your settings. This setting affects only the view that is shown when the resource is opened. 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 not selected. To save the setting but not close the 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 “Searching the topology map” on page 133 “Printing topology maps” on page 133 “Exporting topology maps” on page 134 “Reordering. The default value is 50. Using the Web interface 137 . This option is selected by default. To reset the settings to the system-defined values. Chapter 2. 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. You still must click OK or Apply to save the restored settings. and hiding palettes” on page 135 Related reference “Topology-relationship descriptions” Topology-relationship descriptions Relationships between different resources are displayed as lines. you can switch to a different view. 3. click Cancel. minimizing. the topology view is the default view. To close the page without saving the settings. 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. it is important to understand that relationship types are differentiated by the lines. As you work with the topology map. By default. click Restore Defaults. Topology map size Specify the dimensions to use for the topology map view. Custom size (pixels) Specify custom dimensions for the topology map view. click Apply.

a Role controls the access rights of a particular user. The following relationships are available: Table 8. a system accesses an image repository. Defined using Shows that a resource was defined using another resource. controlled by For example. a storage volume is allocated from a storage pool. Applies to Shows that a resource applies to another resource. Contains Shows that a resource is contained by or contains another resource. a platform manager controls a host or a virtual farm. Allocated from Shows that a resource is allocated from or allocates another resource. Advertises Shows that a certain capability is available on a system. Controls access to Shows a resource that controls access of another resource. a firmware update fixes a system. hosts are federated by a virtual farm. a virtual server is hosted by a host. a DVD drive is assigned to a virtual server. For example. For example. Connected to Shows that a resource is connected to another resource. Configured using Shows the settings that have been used to configure a specific resource. a host contains a physical processor or a rack contains a chassis. For example. Fixes Shows the resource that fixes another resource. For example. For example. or assigns another resource. software. For example.. 138 IBMSystems Director Systems Management Guide . Boots from Shows the link between an operating system and the file system from which it is loaded. or fix. Federates Shows a logical relationship between two resources. Resources that exist independently are federated by a separate entity to create a logical contain relationship. Controls/ Shows that a resource is controlled by. For example. For example. For example. or controls another resource. a specified IP address was bound to the given TCP/IP port. For example. Types of relationship lines in the topology map Type Description Accessed via Shows that a resource is accessed from. if a system offers a Web service. Latest for This relationship represents that the given Software Module is the latest for the given computer system. Hosts/hosted by Shows that a resource is hosted by or hosts another resource. a software instance is one of the instances that were configured during of a general Software Installation. a software product can be applied to a system. Assigned to Shows that a resource is assigned to. Configures Shows that a resource template was used to configure an instance of a resource. a system is connected to a network through a particular port. Binds to Shows that a setting is bound to a specific resource. For example. For example. or accesses another resource. an operating system is installed on a server. and a computer system. it might advertise that Web service capability. For example. Installed on Shows the relationship between an operating system. For example. a template was defined using specific configuration settings. For example. Installed as Shows that a software module was used and installed as a specific software resource.

Recommended for Shows that the given Software Module is recommended for the given System. a host processor realizes a virtual processor allocation. Member of Shows membership of a group or other container. Realizes/realizes Shows that one resource provides the physical reality of another by resource. 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. an update might have three requisite updates that must be installed at the same time. a blade server is a member of a BladeCenter chassis. For example. For example. an update might be needed by an operating system. For example. Represents Shows that the given Software Module is considered represented within the Software Installable. This view is available for all resources from the Actions menu and from the resource’s pop-up menu. minimizing. Performs Shows the entity that performs a service. Runs on Shows that a resource runs on another resource. Needs Shows that a Software Module is missing from the System and must be applied to it. or a system performs a particular role. such as a domain name server. Requires Shows that a resource requires or is required by another resource. Plugs into Shows that the given resource plugs into the provided Slot. a virtual server uses a processor allocation. For example. 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. Using the Web interface 139 . Chapter 2. an update might be more recent than another and therefore supersedes it. Provides Shows that this Service is provided by the System. For example. Supersedes Shows that a Software Resource is considered to be a superset of another Software Resource and is therefore superseding it. For example. a set of processes perform a service. Uses/used by Shows that a resource is used by another resource. For example. Using the properties view. 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. you can access troubleshooting information and other important details about a resource from anywhere in the IBM Systems Director Web interface.

thresholds. 3. You can determine applied activities that affect a specific resource in the properties view. Navigate to the resource that you want to view and edit. Right-click the resource and click Properties. The Edit window opens and displays the properties. When you are satisfied with your changes. 4. you can edit it in the properties view. 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. The editable properties are displayed in fields and lists. To edit a property. activations. click OK to save the changes. The General page is displayed by default in the properties view. Only some of the properties are editable. 140 IBMSystems Director Systems Management Guide . Edit one or more of the editable properties. 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. The properties vary depending on the resource. complete the following steps: 1. Click Edit at the bottom of the General page. 5. 2. software packages. such as jobs. or event automation plans.

On the Properties page. click the General tab to view the General page. Click OK. 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. Select the resource for which you want to view the applied activities. click the Applied Activities tab. In the Edit Properties window. 3. 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. complete the following steps: 1. 4. 2. if the General page is not displayed. software packages. Using the Web interface 141 . 2. right-click the group that you want to update. Click OK. Chapter 2. On the Properties page. In the Edit Location window. select the boxes next to the information that you want to update. click Location. Note: Only the information in the fields that you select will be updated.To view the applied activities associated with a resource. Changes made to other fields will not be saved. 2. To edit the location information for a system. To edit the location information for all of the systems in a group. thresholds. Make the updates to the location information. 5. The Applied Activities page displays a list of any jobs. Click Edit. In Navigate Resources. 4. In the Additional Properties area. 3. Click Actions → Properties. activations. make the updates to the location information. complete the following steps: 1. 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. 5. 3. complete the following steps: 1. and event automation plans that are associated with the resource. You can edit location information only if you have installed and activated the Service and Support Manager plug-in or the Active Energy Manager plug-in. Click Edit Location.

Details. a user selection that displays additional controls or options. This option is selected by default. you can set the following preferences: Show palettes on initial view Select to display the Overview. the default topology and table sizes. you will see the topology map without the palettes. you can customize the topology map view by minimizing or reordering the Overview. This option is selected by default. 2. 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. a table completes a sort. Remember palette state Select to make sure that the state of your palettes persists even as you navigate away from the topology map view. you can show the palettes again by clicking the Show Palette View icon on the navigation toolbar. the topology view is the default view. and Filter palettes in the topology map view. expand Settings and click Navigation Preferences. you can switch to a different view. These preferences include the way that topology map palettes are displayed. By selecting Remember palette state. such as fixed column width. or a user starts a page refresh. change to another page in the overall IBM Systems Director Web interface. Enable tables for accessibility Select this option to turn off table features that are not accessible in the interface. Details. This setting affects only the view that is shown when the resource is opened. your preferred topology icon size. 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. and more. Examples of situations that can cause a notification sound include a page refreshing dynamic data. complete the following steps: 1. If you deselect this setting. On the Navigation Preferences page. By default this option is not selected. After you have opened the resource. For example. you maintain the customized view of your palettes even after you log out of the IBM Systems Director Web interface. Remember last size used Specify that you want to save the dimensions of the current 142 IBMSystems Director Systems Management Guide . or log off from the IBM Systems Director Web interface. and Filter palettes. Topology map size Specify the dimensions to use for the topology map view. 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. To set the navigation preferences. By default this option is not selected. In the IBM Systems Director Web interface navigation area. By default.

click Cancel. Custom size (pixels) Specify custom dimensions for the topology map view. The default number of rows is 10. When you are satisfied with your settings. 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 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. click Apply. click Restore Defaults. Using the Web interface 143 . topology map view and use these dimensions at the next startup. To save the setting but not close the page. Preferred size for topology map icons (pixels) Specify the size of icons in the topology map when the map is displayed initially. To reset the settings to the system-defined values. Chapter 2. The default value is 50. This option is selected by default. 3. To close the page without saving the settings. The default number of rows is 15. You still must click OK or Apply to save the restored settings. click OK to save the settings and close the page.

If the name that was set for the resource when it was discovered is not easily usable for you. 3. 2. Then. you can rename the resource. Select the resource. 4. type the new resource name. The selected resource is renamed in the IBM Systems Director database. In the Rename window. click Actions → Rename. To rename a resource in the IBM Systems Director database. 144 IBMSystems Director Systems Management Guide . click OK. 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. In the name field. Navigate to the resource that you want to rename. complete the following steps: 1.

To remove one or more resources from the IBM Systems Director database. Chapter 2. The selected resource is removed from the IBM Systems Director database. If the property does not permit removal. A confirmation message is displayed. 2. Resources have a properties that determines whether they can be removed. Then. However. complete the following steps: 1. 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. click Actions → Remove. Navigate to the resource that you want to remove. In the Remove window. Click OK. 4. Using the Web interface 145 . Select the resource. OK. 3. removing a resource from the database is useful when you are removing a resource from your systems-management environment. this task is not available for the resource.

wizards. you can automatically run tasks on groups of resources. Groups are displayed in Navigate Resources. You can schedule tasks to run on groups of resources. and throughout the IBM Systems Director Web interface. and export customized groups of resources. import. Using an event automation plan. Depending on the type of group that you create. edit. Health Summary. Groups have the following general characteristics: 146 IBMSystems Director Systems Management Guide . You can create. you can use groups to easily identify and categorize new resources when they are discovered. 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. 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.

For example. Dynamic groups Dynamic groups are based on specified system criteria. IBM Systems Director Server does not automatically update the contents of a static group.v Groups can include resources. Chapter 2. v Groups can include other groups. a dynamic group might contain all systems that have Linux installed. v Resources can belong to multiple groups. Static groups Static groups contain a specified list of systems. the dircli chgp command. the resources that are members of that group are displayed. or an event automation plan. Related concepts “Default or predefined groups” “Groups member types” on page 152 Default or predefined groups When you start Navigate Resources. 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 members of a static group are fixed unless you change them using the IBM Systems Director Web interface. Note: You cannot edit or delete static default groups. the discovered resources are categorized and displayed in default groups. Using the Web interface 147 . You can create a dynamic group by specifying criteria that the attributes and properties of the systems must match. v When you select a group in Navigate Resources. You also can copy the members of any dynamic group to a static group. For example. v You can perform tasks on groups in order to perform the task on every group member. You can click a group to view subgroups that further categorize the resources for ease-of-use. a static group might contain all the systems that are physically located in a particular server room. 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.

Scalable Virtual Servers and Members . They are displayed in the Power Server group that is contained in the IBM Power Systems group. Groups by System Type Systems categorized into subgroups by hardware and operating system platform. switches. The available subgroups vary. All Systems All discovered systems in IBM Systems Director. including servers. All Operating Systems All operating systems that can be managed in the IBM Systems Director. blades. – 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 . and storage systems. operating systems. chassis.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 . depending on the plug-ins that you have installed in your IBM Systems Director environment. Note: You cannot edit or delete static default groups. 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.

event automation plans that use threshold values are migrated to this group. These subgroups include the Favorites group. For information.1. see “Storage groups. 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 No Access v Systems with Partial Access v Systems with Full Access Groups with Thresholds Any groups to which you have applied a threshold. Personal Groups Any groups that you have created or are exclusively associated with your IBM Systems Director user ID. Chapter 2. Note: The JS21 and JS22 blade servers are displayed in this group also. Note: If you have migrated event automation plans from versions of IBM Director earlier than version 6. Other Groups Group definitions migrated from versions of IBM Director earlier than version 6.1. 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.” – 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. Using the Web interface 149 . – 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.

machine type. such as the type of resource. see “Virtualization groups. Update Groups All groups provided by update manager. make a copy of one that you want to change and make changes to the copy. For more information on Service and Support Manager groups. model.” Storage groups: These predefined storage groups are shipped with IBM Systems Director so that you can start working on storage configuration quickly. This default group provides the following dynamic subgroups: Eligible Systems Contains resources that Service and Support Manager can monitor. machine type. Systems with Service Requests Contains resources for which a service request has been opened with IBM® Support. The eligibility of a resource depends on many factors.” Virtualization Groups All groups provided by virtualization manager.” 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. For information. Monitored Systems Contains resources that are being monitored by Service and Support Manager. The eligibility of a resource depends on many factors. Excluded Systems Contains resources that are ineligible for monitoring by Service and Support Manager. manufacturer. model. Instead. BladeCenter Storage Contains all systems that have IBM BladeCenter S SAS RAID Controller 150 IBMSystems Director Systems Management Guide . Service and Support Manager categorizes systems into subgroups based on their service monitoring status. and can understand which systems have which storage devices attached. see “Service and Support Manager. Service and Support Manager has not been able to determine the resources’ eligibility because the resource information is not available. For information. and serial number. You can see the Service and Support Manager for information on starting monitoring for an eligible system. such as the type of resource. see “Update groups. Unknown Systems Contains resources for which Service and Support Manager eligibility is undetermined. and serial number. manufacturer. but are not currently being monitored. Do not delete or make changes to these predefined storage groups.

These are the SAN systems. Systems and Volumes Computer system volume to storage subsystem volume topology. 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 this group changes as update information changes. They could be systems with traditional adapter cards. Storage Subsystems and Volumes Storage subsystem volume to computer system volume topology. Static update groups can be used as a baseline for future comparison or update deployment. IBM BladeCenter S SAS RAID Controller Module storage is included in this group as well as in the BladeCenter Storage group. Dynamic update groups Automatically contains updates based on selected update types. SAS storage systems. Using the Web interface 151 . If you add a system group or an update group to an existing system group or update group. 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. They could be Fibre Channel. The following table lists the names and descriptions of the groups provided by virtualization manager. Module storage for IBM Systems Director. SMI-S Providers Contains all systems that have SMI-S providers installed and running. Both types can be used in compliance policies. Virtualization manager provides a set of default or predefined groups for virtual resources. Chapter 2. The membership of the update group is resolved at the time that the task runs. this new. Local Storage Contains all systems that have Internal RAID Controllers installed. Static update groups Contain individual updates that were explicitly chosen. Update groups: Update groups can be static or dynamic. Once established. Network Storage Contains all discovered external storage systems. or IBM BladeCenter systems with RAID daughter cards. the membership changes only when you manually add or delete updates. Virtualization groups: IBM Systems Director organizes logical sets of resources into groups. or iSCSI systems. nested group will not be considered when the parent system or update group is used for validation of compliance policies. An example is a system that has installed the SMI-S Provider for IBM® Storage System DS4000.

Managed System Contains resources that are managed in IBM Systems Director by way of Common Agent or Platform Agent. You can create a dynamic group by specifying criteria that the attributes and properties of the systems must match. Agentless-managed systems are also included. The criteria available for selection are derived from inventory.” Then. groups have a member type that restricts the kind of resource that can be a member of the group. For example. or relationships Virtual Farms Virtual farms Groups member types In IBM Systems Director. Note: This member type is not available for dynamic groups. Virtualization manager groups Group Description Virtualization Groups Groups for managing virtualization Platform Managers Systems capable of managing hosts or farms Platform Managers and Members Platform managers and their hosts or farms Hosts Systems capable of hosting virtual servers Virtual Servers Virtual servers Virtual Servers and Hosts Virtual servers and their hosts Guest Operating Systems Operating systems running on virtual servers Virtualization Systems Systems with virtualization capabilities. Update Contains software and firmware updates. create an event automation plan 152 IBMSystems Director Systems Management Guide . 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 quickly group existing systems by creating a dynamic group using the criterion Windows operating system. 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. Table 9. Group Contains other groups. The following member types are available: Any Contains all resources. if a group is assigned the member type Server. then only resources that are servers can be members of the group. 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. For example. attributes.

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

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

controllers. you can create a static group. From the Member type list. Group Group membership is limited to other existing groups. and storage. operating systems. fabric. 5. and operating systems. you can create a static group for all the servers that you are responsible for in your systems-management environment. IBM Systems Director. Groups also can contain other groups. select Static from the Group type list. including systems. 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. complete the following steps: 1. Optionally. 3. the Welcome page is displayed. Using the Web interface 155 . you also can type a description of the group. Update Group membership is limited to updates types such as for firmware. click Navigate Resources. In the IBM Systems Director navigation area. For example. From the Location list. you can have a group called Development Systems that contains three groups: one group for each development team. and management applications. a parent group is created and is located under Personal Groups. Managed System Group membership is limited to system types such as different type of servers. 4. In the Group Editor wizard. A member type acts like a filter. Only resources of the specified type can be part of the group you are creating. 6. select the type of member that you want included in the group. Click Next. 2. click Create Group. On the Type and Location page. chassis. select the parent group to contain the group that you are creating. In Navigate Resources. 7. To create a static group. Chapter 2. Click Next. Any Group membership is unlimited. type a unique descriptive name for the group that you are creating. On the Name page. switches. For example. farms. Any resource can be in the group. In Navigate Resources. software. hardware control points.

10. click Back. You also can drill down into a group and select one or more resources. In the Group Editor wizard. You cannot add a group’s parent to itself. you can edit the name and description of the group. 3. then the selected resource is not a valid selection due to its member type. then you cannot add Personal Groups to Group1. select one or more groups of resources from the Available list and click Add. Click Actions → Edit. Click Next. For example. If you are editing a dynamic group. 156 IBMSystems Director Systems Management Guide . click Navigate Resources. In the IBM Systems Director navigation area. If you need to make changes. If you are editing a static group. Note: You cannot edit default or predefined groups. otherwise. If you select a resource to add. click Finish. select it from the Selected list and click Remove. If you want to remove a group or resource. you can edit the members of the group. 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. but the Add button is unavailable. On the Summary page. if you define the parent group location for Group1 to be Personal Groups. 2. On the Define page. 9. To edit a group. Notes: a. you can edit the membership criteria. If you are editing a static group. If you are editing a dynamic group. b. Click Next. 11. complete the following steps: 1. you can edit the membership criteria. 8. A confirmation message about the group creation is displayed also. verify the details of the group. The static group is created and is displayed in Navigate Resources. you can edit the members of the group.

click Finish. 2. 3. Click Actions → Delete. otherwise. the next time you open Health Summary. The group is updated with your changes and is displayed in the Navigate Resources. Attention: The group will be deleted for all IBM Systems Director users. Select the group that you want to delete. A confirmation message about the group change is displayed also. Chapter 2. While you can delete the Favorites and Health Summary groups. the job remains and is active. 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. they will not have any members. The group is deleted and is no longer displayed in the Navigate Resources. click Navigate Resources. verify your changes to the group. click < Back. Using the Web interface 157 . complete the following steps: 1. Click Delete to delete the group. In the IBM Systems Director navigation area. A confirmation message is displayed. Note: You cannot edit or delete static default groups. the groups are recreated. However. 4. If you delete a group that was used when scheduling a job. On the Summary page. If you need to make changes. 4. To delete a group. but it does not run because it does not have a target system against which to run.

2. complete the following steps: 1. 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. 5. A confirmation message about the addition is displayed. Select one or more resources. click Actions → Add to → Existing Group. 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. v The selection is not a group. Then. v The resource might already be a member of that group. If you want to remove a group or resource. To add one or more resources to an existing static group. Click View Group to view the affected group immediately. click Navigate Resources. Navigate to the resource or resources that you want to add to a static group. In the IBM Systems Director navigation area. select it from the Selected list and click < Remove. The selected resources are added the static group. You also can drill down into a group and select a subgroup. select one or more groups from the Available list and click Add >. You can select only a 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. In the Add to Existing Group window. 158 IBMSystems Director Systems Management Guide . Note: If the Add > button is unavailable. 4. 3. Click OK. but an individual resource.

If your Web browser requires a location selection. Select one or more groups that you want to export. In the file download window for your Web browser. provide it and click Save. After a group is exported. 3. complete the following steps: 1. In the IBM Systems Director navigation area. To export a group. Chapter 2. Using the Web interface 159 . click Navigate Resources. 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. 4. Click Actions → Export Groups. click Save to disk and then click OK. 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. 2. 5. you can distribute it to a new instance of IBM Systems Director Server by importing the group through the IBM Systems Director Web interface. The group is exported and an XML file is saved to the location that you provided.

In the IBM Systems Director navigation area. 4. type the file name in the Select the file that you want to import field. 3. make sure you use Group Export to export the group in the earlier version of IBM Director. select the imported group and click Actions → Add to Existing Group. 2. Note: To import groups from versions prior to IBM Systems Director 6. When the import is completed. If you want to view the imported group in another group than Personal Group. In the Group Import page. Click Actions → Import Groups. complete the following steps: 1. click Navigate Resources. Or.1. To import a group. 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. A progress indicator is displayed. a confirmation message is displayed and the group is displayed in the Personal Group in Navigate Resources. Click OK. 160 IBMSystems Director Systems Management Guide . click Browse to navigate to the exported group file that you want to import.

These tasks are launched tasks and are identified on menus by the Launched tasks icon . When you select a launched task. 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. 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. Using the Web interface 161 . the task can be displayed in one of the following ways: Chapter 2.

For more information see “Security. To find a task. see “Downloading Java Web Start. The Find a Task page opens and displays an alphabetical list of all available tasks in your IBM Systems Director installation. or in pop-up menus. In the IBM Systems Director Web interface navigation area. v The IBM Systems Director Launched Tasks program is displayed and opens the task that you selected. Because the IBM Systems Director Launched Tasks program opens outside of the IBM Systems Director Web interface. If it is a targeted task. Java Web Start (JWS) is also provided for installation. v In another instance of your Web browser. click Find a Task. Note: Find a Task is also available on the Welcome page.” 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.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. you must also have authorization to access the systems.” To find tasks quickly in the IBM Systems Director Web interface. IBM Systems Director provides some tasks that still require a client-based application. While many tasks can be found in the IBM Systems Director Web interface navigation area. 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 . a list of available target systems is provided. you can quickly and easily find any task using Find a Task. v As a separate program on your system desktop. 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 . The task provides its own Web interface. you can run the selected task. 2. you must be authorized to use that task. If you do not know the name of the task you want. If it is a targeted task. For more information. the Actions menu. Then. complete the following steps: 1.

Start a task from the IBM Systems Director Web interface navigation area in any of the following ways: v Click Find a Task. Click the task that you wanted to find to start it.” v Expand the sections in the navigation pane to view and click available tasks. If the task requires a resource on which to work.” Note: You can select a noninteractive task and click Actions → Run to schedule the task to start immediately or at a later time. see “Scheduling tasks. For more information. All of the table columns are searched for the word that you typed. 4. 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. type the task name in the Search the table field and click Search. On the Find a Task page. Any pages that you have saved to your Startup page are displayed here. For more information. Chapter 2. For more information. v Expand Task Management and click External Application Launch. You can configure other applications to run from the IBM Systems Director Web interface. If you know all or part of the name of the task you want to find. right-click a resource and select a task. see “Integrating external applications. 3. Any task that has the entered word in any of its columns is displayed. see “Finding a task. see “Customizing the Web interface. then the task opens immediately. Using the Web interface 163 . If the task does not require a resource.” v Click any of the tasks available in the navigation area. A saved page includes any tasks that can be run from that page. you can search for and start a specific task. Start a task from the IBM Systems Director Web interface content area in any of the following ways: v In a table view. you want.” v Click My Startup Pages. For more information. the task will request the resource.

select the resource. v In the topology map view. 164 IBMSystems Director Systems Management Guide . 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 your Web browser does not have JWS installed already. in the Details palette. If your Web browser has a version of JWS installed that is not compatible with 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. Tip: You can run some tasks on multiple resources simultaneously. select one or more resources. a prompt is displayed to download and install JWS. Java Web Start (JWS) is required. For more information. right-click a resource and select a task. right-click the resource and select a task. If your Web browser has a version of JWS installed that is not compatible with 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. you can select Run Now or Schedule. see “Scheduling tasks. For more information. select one or more resources. This program is installed automatically the first time you use a task that requires it. a prompt is displayed to download and install JWS. Then. v In a table or topology map view. To perform a task on multiple resources. Because the IBM Systems Director Launched Tasks program opens outside of the IBM Systems Director Web interface. see “Starting the IBM Systems Director Launched Tasks program. You can schedule a task to start immediately or at a later time. click Actions and click a task. If your Web browser does not have JWS installed already. v For applicable tasks. This program is installed automatically the first time you use a task that requires it. a compatible version of JWS is installed automatically. v In the topology map view. Java Web Start (JWS) is required. Then. right-click one of the selected resources and select a task. Then. Because the IBM Systems Director Launched Tasks program opens outside of the IBM Systems Director Web interface. a compatible version of JWS is installed automatically.

” 3. Start a launched task. Using the Web interface 165 . Note: When starting tasks from the IBM Systems Director Web interface using Mozilla Firefox. if the Java Web Start installation does not succeed as expected. an automatic installation of the IBM Systems Director Launched Tasks program starts. Download the Java Web Start software to your browser system. For more information.jnlp window might open and display a message asking what to do with the .” 2. If you are starting a launched task for the first time on your browser system.However. it is recommended that you select Open with Java Web Start Launcher and Do this automatically for files like this from now on. Make sure that your browser system is configured to use Java Web Start. 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. To make sure that the launched task can proceed and that this message is not displayed in the future. see “Configuring Web browsers to use Java Web Start. the Opening launch.jnlp file. Chapter 2. For more information. see “Downloading Java Web Start.

a message window is displayed. Click Download Now. If your browser system requires JWS. For Linux 1. 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. Complete the following applicable steps. JWS is required on your browser system to enable launched tasks in IBM Systems Director. Option Description For Windows and AIX Click Download Now. complete the following steps: 1. 2. To download JWS. the Java Web Start (JWS) software must be installed on your browser system. 166 IBMSystems Director Systems Management Guide . Select the applicable (Java Runtime Environment) JRE for your browser system.

select Open them with this application and click Browse. When the JWS installation is complete. 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. located in the IBM® JRE directory. Select to save the file to your hard disk drive or open and run the file immediately. complete the following steps: 1. Note: If the JNLP file type is not available. select the javaws. 4. javaws. In the Download Actions window. click OK. retry the launched task that you wanted to use. to use the IBM® Java Web Start program. 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. version 2. 3. the Firefox Web browser must use the IBM® Java Web Start program that is installed with the IBM® Java Runtime Environment (JRE). 6. To update the Firefox Web browser. In the Web browser. Navigate to the Java Web Start program.2. Using the Web interface 167 . as applicable for your operating system.6. including those that use the IBM Systems Director Launched Tasks program.” 5. In the Change Action window.exe program and click Open. In the Download Actions window. including those that use the IBM Systems Director Launched Tasks program. select the JNLP file type and click Change Action.0. Web browsers must use the IBM® Java Web Start program that is installed with the IBM® Java Runtime Environment (JRE). 2. click Close. On the Content page. Chapter 2. 7. In the Change Action window. In the bin directory. 9. 8. see “Associating the JNLP file type with the Java Web Start program (Firefox). In the Options window.0.exe. click Tools → Options. 3. click Manage. click Content from the toolbar.

complete the following steps: a. complete the following steps: 1. To associate the JNLP file type with the Java Web Start program. you must associate the JNLP file type with the IBM® Java Web Start program. 3. Click OK. located in the IBM® JRE directory. you determine that the JNLP file type is not available for configuration by way of the Firefox Web browser.” 5. while updating the Firefox Web browser to use the IBM® Java Web Start program. select the JNLP file type and view the information in the Details area. versions 6. click OK. 6. 4. In the Open with list. is restored. complete the following steps: 1. Click Restore. Start the Windows Explorer program. The default behavior for JNLP files. opening with the Java Web Start executable. including those that use the IBM Systems Director Launched Tasks program. In the Opening launch. see “Associating the JNLP file type with the Java Web Start program (MSIE). click the File Types tab. to use the IBM® Java Web Start program. 10. 6. the Microsoft Internet Explorer Web browser must use the IBM® Java Web Start program that is installed with the IBM® Java Runtime Environment (JRE). In the Edit File Type window. In the Options window. 4.jnlp window. 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. 2. In the Folder Options window. Note: If the JNLP file type is not available. 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.0 or 7. Click Tools → Folder Options. 168 IBMSystems Director Systems Management Guide . In the bin directory. Navigate to the Java Web Start program. 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.0. To update the Microsoft Internet Explorer Web browser.exe program and click Open. javaws. click Do this automatically for files like this from now on. select the javaws. 2. Click the IBM Systems Director task that required Java Web Start. b. 5. Click Advanced. select Other. click Edit. The task launches.exe. On the File Type page. 3. If the Details area reports that the JNLP file type has customized behavior.

11. In the Folder Options window. while updating the Microsoft Internet Explorer Web browser to use the IBM® Java Web Start program. In the File Extension field. 17. 6. you determine that the JNLP file type is not available for configuration.exe program and click Open. 12. click the File Types tab. 7. In the Editing action for type window. Click OK. 11. In the Edit File Type window. In the Action field. 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. Click Browse. In the Topic field. 2. 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. click Browse. 5. Click OK. type System. javaws. 14. select the javaws. On the File Types page. In the Folder Options window. 8. 3. 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. Chapter 2. 15. javaws. In the Edit File Type window. In the Edit File Type window. Navigate to the Java Web Start program. you must associate the JNLP file type with the IBM® Java Web Start program. click New. Using the Web interface 169 . 7. select the javaws. click OK. type &Launch. Click Tools → Folder Options. 16. 10. 13. To associate the JNLP file type with the Java Web Start program. type javaws. In the bin directory. select JNLP in the Registered file types list and click Advanced. select the Use DDE check box. 9. 13. 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.exe. Start the Windows Explorer program. type jnlp and click OK. On the File Types page. 9. located in the IBM® JRE directory. In the bin directory. 4. click Close. In the Folder Options window. 12. In the Application field.exe. located in the IBM® JRE directory. 10. In the New Action window. click OK.exe program and click Open. 8. Navigate to the Java Web Start program. clear the Confirm open after download check box and click New. click Close. In the Editing action for type window. complete the following steps: 1.

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. 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. configuring SSL ensures data integrity and data confidentiality between the management server and Web browser client.” 2. by default. see “Requesting a CA signed certificate” and “Receiving a CA signed certificate. If these host names do not match. a Secure Sockets Layer (SSL) certificate that supports HTTPS connections between IBM Systems Director Server and the Web browser client. by default. 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. It is not required that you use SSL to secure the network traffic between your management server and client browser. Update the Web browser with the new certificate. 170 IBMSystems Director Systems Management Guide . You must delete this default certificate before you can replace it with either a self-signed certificate or a CA signed 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. Delete the default certificate. However.” 3. 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. you must change the keystore password. For information see “Deleting the default certificate. Create a new certificate. Also.” 4. complete the following steps: 1. if you specify a long name for the host name in the Common Name field of the certificate. You can create either a self-signed certificate or request and receive a CA signed certificate. you must specify a long name in the URL. For example. to ensure server authentication. see “Creating a self-signed certificate. and data integrity. you might receive errors when you try to open the Web interface or start launched tasks. To replace the default certificate with a new certificate and to change the keystore password for SSL. v To create a self-signed certificate. Update the Web container properties. However. data privacy. For information see “Updating the Web container properties. a Secure Sockets Layer (SSL) certificate that supports HTTPS connections between IBM Systems Director Server and the 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.” v To request and receive a CA signed certificate. For information see “Updating the Web browser with the new certificate.

jks where install_root is the root directory of your IBM Systems Director installation.” v If you want to request a CA signed certificate. The default keystore file password for IBM Systems Director is ibmpassw0rd. Note that this path uses the backslash (\) to delimit the directory. In the Services pane. Note that this path uses the backslash (\) to delimit the directory. you must create a new certificate. Option Description For Linux install_root/jre/bin/ikeyman For Windows install_root\jre\bin\ikeyman. Click Browse and navigate to the applicable default keystore file: Option Description For Linux install_root/lwi/security/keystore/ ibmjsse2. In the Key database type list. select the default personal certificate named lwiks and click Delete. To open the default keystore file. In the Password Prompt window. you might be required to enter the path using the forward slash (/). To delete the default certificate.” Chapter 2. specify the default password for the default keystore file and click OK. depending on the system that you are using. click OK. 3. Right-click My Computer and select Manage. right-click IBM Systems Director Server and select Stop. go to “Creating a self-signed certificate. In the Computer Management window. 2. then. you might be required to enter the path using the forward slash (/). Exit from the Computer Management window. Next. 5. Stop IBM Systems Director Server by completing the applicable steps: Option Description For Linux Type the following command: smstop For Windows 1. In the Key database content pane. click Key Database File → Open. depending on the system that you are using. 8. 2. 4. Start the IBM® Key Management program by typing the applicable command. expand Services and Applications → Services.jks For Windows install_root\lwi\security\keystore\ ibmjsse2. see “Requesting a CA signed certificate. v If you want to create a self-signed certificate. 6. 4. complete the following steps: 1.exe where install_root is the root directory of your IBM Systems Director installation. 7. Using the Web interface 171 . select JKS. 3.Note: Back up any files before you edit them. Select the default keystore file and click Open.

Next. In the Change Password window. accept the default value. you must specify a short name for the Common Name. use self-signed certificates only on a temporary basis while you test your environment. 10. Important: If you want to request a CA signed certificate. click Create > New Self-Signed Certificate. Therefore. You can replace the default certificate with a self-signed certificate. if you use a short name in your URL. select X509 V3. 11. 3. Messages and settings might differ depending on your Web browser and the version of Java Web Start that you are running. in the Key Label field. 7. In the Create New Self-Signed Certificate window. 9. specify the lifetime of the certificate in days or accept the default value. In most cases. you must delete the default certificate.” 172 IBMSystems Director Systems Management Guide . To exit the IBM® Key Management program. DirServer. In the Validity Period field. they are not considered publicly trusted certificates. In the Common Name field. 8. you must update the Web container properties. Instead. Back up any files before you edit them. for example. 2. Because anyone can create self-signed certificates. click Key Database File → Exit. specify the fully-qualified host name of the server for which you are creating the certificate. Go to “Updating the Web container properties. 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. specify a label for the new certificate. Click OK. In the Organization field. 12. 2. complete the following steps: 1. click Key Database File → Change Password. you can use it immediately. do not perform this procedure. In the Country or region list. 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. type the name of your organization.” Notes: 1. In the Version list. After you create a self-signed certificate. However. For information see “Deleting the default certificate. 4. you must specify the fully-qualified host name. In the IBM® Key Management program. see “Requesting a CA signed certificate. In the Key Size field. Before you complete this procedure. accept the default value. specify and confirm a new password and click OK.” To create a self-signed certificate. 5. To change the default keystore file password. 6.

specify the fully-qualified host name of the server for which you are creating the certificate. In the Create New Key and Certificate Request window. However. In the Country or region list.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). To create a certificate-signing request. Using the Web interface 173 . click Create → New Certificate Request.” Chapter 2. In the Enter the name of a file in which to store the certificate request field. complete the following steps: 1.” Important: If you are creating a self-signed certificate. you must delete the default certificate. Therefore. For information see “Deleting the default certificate. In the Common Name field. for example. DirServer. do not perform this procedure. 4. for example. in a production environment. You must create a certificate-signing request (CSR) to request a digital certificate from a CA.arm. However. Click OK. type a label for the new certificate. In most cases. 6. this type of certificate is better suited for your production environment. 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. you must request a production certificate. You can request either a test certificate or a production certificate from the CA. you must specify a short name for the Common Name. 9. 7. In the Organization field. 5. 8. Because certificate authorities are public entities that issue certificates to identify other entities. accept the default value. accept the default value. in the Key Label field. In the IBM® Key Management program. 2. See the CA Web site for specific instructions about requesting a new certificate. Send the certificate-signing request file to the CA. 3. Next. you must specify the fully-qualified host name. DirServerSecPubCertreq. type a file name or click Browse to select a file in which to store the certificate request. you must receive the CA signed certificate. Go to “Receiving a CA signed certificate. if you use a short name in your URL. In the Key Size field. type the name of your organization. Before you complete this procedure. CA signed certificates provide a level of public trust.

2. For information see “Requesting a CA signed certificate. Note that this path uses the backslash (\) to delimit the directory.arm from a CA into the IBM® Key Management program. You must receive and save the new certificate in the default keystore file. Before you complete this procedure. Go to the IBM® Support and Download Web site at www. depending on the system that you are using. This procedure documents how to receive a signed certificate with a file extension of .com/support/us and search using the document number SC23-6510-00. Go to the IBM® Support and Download Web site at www. DirServerSecPubCert. Back up any files before you edit them. see Resolving the iKeyman Corrupted Database Message. For example. Note: The e-mail message from the CA might include supplemental text in front of the certificate and after the certificate. 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. Messages and settings might differ depending on your Web browser and the version of Java Web Start that you are running. 174 IBMSystems Director Systems Management Guide . Important: If you are creating a self-signed certificate.” Notes: 1.pfx and errors indicate that the certificate store is corrupt.arm. make sure that you cut and paste the supplemental text along with the certificate text.ibm. If your certificate has a different file extension. complete the following steps: 1. 3. 2.ibm. To receive a CA signed certificate. for example. do not perform this procedure. you must create and submit a certificate-signing request. you must cut and paste the certificate from the e-mail message and save it in a certificate file. 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. If you are importing a certificate with a file extension of . If the CA sends the new certificate to you as part of an e-mail message. see the IKeyMan User’s Guide. the CA processes the request and verifies your identity. you might see the text BEGIN CERTIFICATE in front of the certificate and END CERTIFICATE after the certificate. The CA sends the signed certificate back to you by way of e-mail. you might be required to enter the path using the forward slash (/).com/support/us and search using the reference number PRS2855. In this case.

12.exe where install_root is the root directory of your IBM Systems Director installation. Chapter 2. In the Key database content pane. click OK. select Base64-encoded ASCII data. specify a label for the certificate. 13. click Key Database File → Open.jks where install_root is the root directory of your IBM Systems Director installation. you might be required to enter the path using the forward slash (/). Click Browse and navigate to the applicable default keystore file: Option Description For Linux install_root/lwi/security/keystore/ ibmjsse2. 5. Optional: Add the public version of the CA signed certificate to the Web browser’s truststore file. Select the default keystore file and click Open. depending on the system that you are using. Note that this path uses the backslash (\) to delimit the directory. 10. Note that this path uses the backslash (\) to delimit the directory. 15. 4. select Personal Certificates from the list. 9. 16. for example. 3. In the Receive Certificate from a File window. depending on the system that you are using. DirServerSec. you might be required to enter the path using the forward slash (/). depending on the system that you are using.arm. Click OK. DirServerSecPubCert. 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. Using the Web interface 175 . The default keystore file password for IBM Systems Director is ibmpassw0rd. in the Data type list. 11. then. 6. 7. Click Receive. In the Password Prompt window. In the Enter a Label window. select JKS. Option Description For Linux install_root/jre/bin/ikeyman For Windows install_root\jre\bin\ikeyman. you might be required to enter the path using the forward slash (/). Start the IBM® Key Management program by typing the applicable command. specify the name of the certificate file that you created when you received the certificate from the CA. specify the default password for the default keystore file and click OK. 14. To open the default keystore file. In the Certificate file name field. In the Key database type list. 17. for example. Click OK. 8.jks For Windows install_root\lwi\security\keystore\ ibmjsse2. In the Location field. Note that this path uses the backslash (\) to delimit the directory.

In the Change Password window. The public version of the certificate contains all identifying information as well as the public key associated with the certificate.” 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. To change the default keystore file password. 19. depending on the system that you are using. Next. This optional step can provide additional security within your SSL configuration. Instead. complete the following steps: 1. Note that this path uses the backslash (\) to delimit the directory. If the browser determines that the certificate is not signed by a trusted signer. Messages and settings might differ depending on your Web browser and the version of Java Web Start that you are running. Configuring SSL for the browser is browser-specific. edit the properties in the sslconfig file. and restart IBM Systems Director Server. specify and confirm a new password and click OK. See your browser documentation for instructions.properties file. 2. Notes: 1. you must update the Web container properties. you must update the Web container properties with the new keystore password. you must create a file named sslconfig in the same directory. To exit the IBM® Key Management program. 20. click Key Database File → Change Password. Go to “Updating the Web container properties. 176 IBMSystems Director Systems Management Guide . the browser displays a warning which alerts you to a possible security breach. you must create a new certificate.” v To request and receive a CA signed certificate. 18. Before you perform this procedure. 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. The Web browser can determine whether the server presents a certificate that is signed by a trusted signer. see “Creating a self-signed certificate. The process of restarting IBM Systems Director Server encrypts the new password in the Web container properties. You can create either a self-signed certificate or request and receive a CA-signed certificate: v To create a self-signed certificate.” To update the Web container properties. see “Requesting a CA signed certificate” and “Receiving a CA signed certificate. click Key Database File → Exit. you do not edit properties directly within the webcontainer. To update the Web container properties. Back up any files before you edit them. you might be required to enter the path using the forward slash (/).

Exit from the Computer Management window. Use the secure port value indicated in your properties file. 7. Use the secure port value indicated in your properties file. Option Description For Linux Type the following command: smstart For Windows 1. After the new webcontainer. you can delete the webcontainer.properties. Change the name of the webcontainer. 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. b. Delete the line sslEnabled=true from the sslconfig file. 8.ssl. Go to “Updating the Web browser with the new certificate. Using a text editor. expand Services and Applications → Services.keyStorePassword. Next. 2. Right-click My Computer and select Manage.properties. Specify only plain text values for the passwords in the sslconfig file. edit the sslconfig file. 2. right-click IBM Director Server and select Start. In the Computer Management window. Save the sslconfig file. Restart IBM Systems Director Server by completing the applicable steps. Using the Web interface 177 . Notes: a.ibm. 5.trustStorePassword. Specify the default password ibmpassw0rd for the truststore file.bak to the sslconfig file.ibm. the sslconfig file is used to automatically create a new webcontainer. 3. Specify com. In the same directory.properties file has been created. 4. 9.secure_port=ibmpassw0rd where secure_port is the secure port that IBM Systems Director Server uses.” Chapter 2.properties file to webcontainer. 3.ssl.bak. in plain text: com.bak file manually.properties. create a file named sslconfig and copy the contents of webcontainer. 4. When you restart IBM Systems Director Server.secure_port=new_password Where v secure_port is the secure port that IBM Systems Director Server uses. you must update the Web browser with the new certificate. IBM Systems Director Server deletes the sslconfig file because it is no longer needed. After you start and connect to IBM Systems Director Server. In the Services pane.properties file and encrypt the new password in this file. 10.

click Next. you must update the Web container properties. 9. In the Security Warning window. For Firefox A Website Certified by an Unknown Authority window is displayed. for example. In the Certificate Import Wizard. on the Welcome page. In the Certificate Import Wizard window. In a Web browser. 10. 2. Before you perform this procedure. the following message is displayed: The application’s digital signature has been verified. Click Accept this certificate permanently and then click OK. go to step 11. Some browsers contain the public version of well known CA signed certificates. click View Certificate. In the Certificate window. The default port is 8421. 1. Continue to step 2. On the Certificate Store page. select the way that you want to store the certificate and click Next. A Security Warning window is displayed. When you use a launched task in the IBM Systems Director Web interface. 5. In the Security Alert window. 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. type the following URL to point to IBM Systems Director Server: http://server_name:port_number/ibm/console. 8. click Yes. 11. On the Summary page. 178 IBMSystems Director Systems Management Guide . Do you want to run the application? Be sure to select Always trust content from this publisher and click Yes. View the certificate to determine whether you want to trust the certifying authority. click OK. In the Certificate window.” To update the Web browser with the new certificate. In the Security Alert window. click Install Certificate. 7. 6. you might see the following message: The security certificate was issued by a company you have not chosen to trust. 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. where server_name is the host name of IBM Systems Director Server and port_number is the port for IBM Systems Director Server. For information see “Updating the Web container properties. click Finish. Option Description For Microsoft Internet Explorer A Security Alert window is displayed. 3. click Yes. click OK. complete the following steps. You Web browser is updated with the new certificate. 4.

” 3. 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. 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. These resources specify the application to be started. you must configure the external application so that it is recognized by IBM Systems Director. Select and start an external application. Before you can start an external application from IBM Systems Director Web interface. Define the external-application task by creating a command-task file. 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. Optional: Specify a national-language task title for the command-task file. complete the following steps: 1. For information see “Specifying national-language task titles. Refresh the external applications. 4. configure the remote IBM Systems Director Web interface for external-application tasks. For information see “Creating a command-task file.” 6.” 2.” 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. see “Authorizing users to IBM Systems Director. For more information. They can start a command. or application that is external to IBM Systems Director and runs on the browser system or management server. For more information. 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. Using the Web interface 179 .” 5. the task title. For more information. see “Refreshing external-application tasks in the IBM Systems Director Web interface. For more information. see “Configuring external-application tasks for browser systems. process. To integrate an external application into IBM Systems Director. and the way that the task is started in the IBM Systems Director Web Chapter 2. 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.

Targeted and untargeted tasks: All IBM Systems Director tasks (including native IBM Systems Director tasks. Targeted tasks Targeted tasks are tasks for which a resource is specified when the task is started. MAC address. interface. External-application tasks can be targeted. untargeted. untargeted. Tasks that are both targeted and untargeted A task can be both a targeted task and an untargeted task. the IP address. If no system attributes are configured. it displays information for that resource only. with behavior reflecting the manner in which the task is started. Untargeted tasks Untargeted tasks are tasks for which no resource is specified when the task is started. and computer name are passed to the application by way of environment variables. When an external application is started as a targeted task. Typically. a targeted task performs an action on the resource specified as the target. it displays information for all resources. Examples of targeted tasks are Remote Session and SNMP Browser. depending on how the task can be started. the available values for each target are passed to the application using environment variables. 180 IBMSystems Director Systems Management Guide . 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. or provide their own interface for selecting resources on which to perform actions. or both. if started from the IBM Systems Director Web interface navigation pane. If one or more system attribute names are configured. tasks added by installing plug-ins. External Application Launch tasks also have resources for each supported language defined in the command-task file. 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. or both.x. information about the specified target is provided. perform actions that apply to all resources.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. Targeted tasks are started by right-clicking a resource and selecting the task. The Inventory task is an example of such a task: if started from a resource’s pop-up menu. and external application tasks) are either targeted.

AIX-based systems and Web addresses use forward slashes (/) as delimiters. v Each parameter must be defined on a separate line. depending on the system that you are using. v No error-checking is performed on command-task files. therefore. v Command-task file names must end with the . so you must be careful when editing them. v Environment-variable values must have only one backslash or forward slash. v You must use ISO 8859-1 character encoding when editing the command-task file. 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. any backslash (\) or forward slash (/) character must be coded as a double backslash (\\) or forward slash (//) (for example. Important: Consider the following information when working with command-task file parameters: v Both parameter names and values are case sensitive. Using the Web interface 181 . Parameters are listed here in alphabetical order.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.x. This information uses backslashes (\) to delimit directories in paths that apply to all operating systems.CMDExt extension. dir c:\\tmp\\backup1 /s). v If a command-task file includes parameters that are no longer supported. Command-task files that are not in this directory are ignored. IBM Systems Director uses the file name to sort the external-application tasks in the IBM Systems Director Web interface. which is not case-sensitive. see “Specifying national-language task titles. File names that are identical with the only variant being spaces and underscores are considered duplicates. the last parameter value in the file is used by IBM Systems Director. Parameter names that do not exactly match expected parameters are ignored.v Command-task files must reside on the management server in the classes/extensions directory. v For information about setting a task title using a national-language string. The sort function replaces spaces in the file name with underscores. you might have to enter the directory path differently than shown. 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 Windows-based systems use backslashes (\) to delimit directories in a directory path.” Chapter 2. v Command-task files use Java-properties-file formatting. the affected parameters are ignored. under the directory in which IBM Systems Director Server is installed. v Do not use underscores in file names. and only one will be displayed as an external-application task in the IBM Systems Director Web interface. v If the same parameter is specified more than once. v The file name and extension are not case sensitive.

0. multi. “Managed-resource types Important: To use this parameter.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. For identifies the type of resources for which the list of managed-resource the external-application task can be types. the following two lines specify that the external-application task can use either a physical platform or a logical platform as a target: Client. then IBM Systems Director Web interface displays the task.x. you for the Client. one. replace x with a unique non-negative integer for each target class. Client.Resource=OperatingSystem Client.Resource must set the Targeted parameter to a valid parameter. see targeted.1. The target type IBM Systems Director. system.Windows or the browser FileExists. then IBM Systems Director Web interface hides the task.x.Resource=Server 182 IBMSystems Director Systems Management Guide . If the file does not exist. Command-task parameters Parameter name Description Allowed values CheckFileExistsNow.Unix). and none|multi are valid values. To define multiple targets.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.Unix The attribute that shows or hides the Possible values are: CheckFileExistsNow. false IBM Systems Director Web interface always displays the task.Table 10. none|one. For example.” value other than none.

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

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

This is the start cmd. wildcard expansion. UNIX or Linux bash –c If this parameter is omitted or set to false. Set this parameter if the external-application application requires an interactive window task in a persistent or advanced command-line syntax. This is the start cmd. UNIX or Linux bash –c If this parameter is omitted or set to false. Chapter 2. the command string is issued without starting a persistent shell. such as shell.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. ShellRequired. false Do not start the The shell is started using one of the external-application following commands: task in a persistent Windows shell.exe /k default value. false Do not start the The shell is started using one of the external-application following commands: task in a persistent Windows shell. any command output to the shell is displayed in a command window that you can scroll and later close. the command string is issued without starting a persistent shell. wildcard expansion. Set this parameter if the external-application application requires an interactive window task in a persistent or advanced command-line syntax.exe /k default value. If this parameter is set to true. If this parameter is set to true.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. any command output to the shell is displayed in a command window that you can scroll and later close. Using the Web interface 185 . such as shell.

set the parameter to: System. and these environment variable names can be used in the CommandString or can be accessed by a script launching the application.Property.Table 10.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. to pass the computer name of the targeted system.Resource target by the command. as an environment variable at launch time. 186 IBMSystems Director Systems Management Guide . Each property is passed types.x=Name where x is the index number assigned to the system property. Each property is assigned a unique environment variable name. For example. for each targeted system chosen. Command-task parameters (continued) Parameter name Description Allowed values System.Property.

or both. Using the Web interface menu. 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. This is the default value. The task can be started by selecting a target system and right-clicking the task. none An untargeted If this parameter is omitted. This is the default value. The task can be started by selecting a target system and right-clicking the task. 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 187 pop-up menu. none|one Tasks that are both targeted and untargeted. or from the pop-up menu. be opened by selecting it in the IBM Systems Director Web interface navigation pane. or can be started by . from the Actions menu. This is the default value. or can be started by selecting a target system and right-clicking the task. an untargeted task. from the Actions Chapter 2. from the Actions menu. from the pop-up menu. one A targeted task. The task can to one.Table 10. the value is set task. multi A targeted task. The task can be opened by selecting it in the IBM Systems Director Web interface navigation pane.

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

Resource parameter specified). CommandString. v A console/server synchronized task runs an interactive task and a noninteractive task. This is especially true if the external-application task targets multiple resources.Server parameter.Resource object).” Tip: Only specify the environment variables that are necessary to start the external application. Note: These tasks must not invoke IBM Systems Director commands. Using the Web interface 189 .x. Note: You are responsible for ensuring the validity and functionality of your environment variables. v To create a group heading to serve as a parent for group of related external-application tasks in IBM Systems Director Web interface. they are considered to be one console/server task. The system properties that are available depend on the target type (Client. each of which has a key and a value. the external-application task must be targeted (that is.x. 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.Resource or System. If you specify more than one target type. Use environment variables to pass system attributes to the external applications. see “Command-task file parameters. To pass system-property values when starting an external application.x.Property parameter. create an interactive task without a CommandString or CommandString. Chapter 2. 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. For information about the Client. the list of available system properties is the union of all available system properties for those target types. Use environment variables to pass system attributes to the external application. ensure that the system attributes are named correctly.Server parameter and a CommandString parameter.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. To create a console/server synchronized task. specify both a CommandString. The interactive task is started after a successful launch of the noninteractive task.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). Because both tasks are required to provide function to a user.Server parameter. The noninteractive task is started first. The CommandString.x. it must have at least one Client. If the task requires that system attributes be passed in the environment. Some system properties (such as computer name) are available for all target types. Each target type provides a set of system properties. You would create a synchronized task when an interactive task depends on a noninteractive task running simultaneously in order to function.

Note that this might not be a complete list. 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. The following table provides an example. 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 11. Table 12. You can access the value associated with a system property using the echo command.

snmp.x. and might not include third-party managed-resource types or resource types supported in future versions of IBM Systems Director.platform.server.Table 12.Platform com.sysmgt.tier.twg.twg.tivoli. IBM Systems Director resources and managed-resource types Managed-resource type Resource OperatingSystem com.complex.tivoli.sysmgt.RIOEnclosure GenericNetworkDevice com.sysmgt.twg.sysmgt.Resource parameter: Managed-resource types are used to specify targets for the external application task with the Client.spm.ibm.” Valid managed-resource types include those listed in Table 13.snmp.BCChassisManagedObject Server com.twg.storage.Resource parameter.TWGSNMPDevice PassThroughModule com.Resource parameter” “Sample command-task files” on page 192 Managed-resource types for the Client.platform.LogicalPlatform com.snmp.tivoli. Note: The information provided in this table is for reference only.Complex Switch com.printer.x.rmon.ibm.StorageManagedObject Chapter 2.Partition Chassis com.platform.SNMPPrinter StorageSubsystem com.twg.engine. see “Command-task file parameters.ibm.chassis.sysmgt.twg.sysmgt.partition. Table 13.tivoli.x.ibm.twg. Using the Web interface 191 .ibm.ibm.PhysicalPlatform com.TWGNativeManagedObject com.sysmgt.bcchassis.tivoli.TWGSNMPDevice Cluster com. For information about this parameter.sysmgt.tivoli.server.spm.ibm.rioe.server. 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.TWGRMONDevice com.tivoli.snmp.TieredManagedObject SystemChassis com.spm.ibm.TWGSNMPDevice Printer com.

CMDExt) This example shows a command task to create a Windows network-drive connection to the targeted system using the next available drive letter. 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 open a Telnet session and hold the window open while a user types the user ID and password.Unix = # Empty command string specified.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.Server. 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.exe %CMDTASK_MO_MFG_0% %CMDTASK_MO_MACHINETYPEMODEL_0% 192 IBMSystems Director Systems Management Guide . # Parameters for all operating systems: Targeted=one ShellRequired=true # Parameters for UNIX and Linux: CommandString. Telnet to managed system (Telnet.Windows = myServerApp.Windows = telnet %CMDTASK_IP_ADDRESS0% Map a managed system to a Windows network drive (NetUse.Unix = xterm –hold –e telnet $CMDTASK_IP_ADDRESS0 # -hold gives you an error message if telnet fails # Parameters for Windows: CommandString. With the –hold option. # Parameters for all operating systems: Targeted=one ShellRequired=false # Parameters for UNIX or Linux: CommandString. # Parameters for all operating systems: #On Windows: CommandString. you also receive an error message if the Telnet command is not performed successfully.

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. see “Considerations for command-string parameters.” For information about the CommandString parameter. complete the following steps: 1.” 4.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. The following line sets a parameter for Windows: CommandString. You can create and modify External Application Launch resource bundles using an editor. see “Command-task file location and naming conventions.CMDExt extension. To create a command-task file. Using the Web interface 193 . for example: # This line is a comment.” 2. Define the task that you want to run using one of the CommandString parameters or define a group heading. 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 a command-task file that is used to integrate third-party management software and other programs with IBM Systems Director. Create a file with the . Save and close the file. see “Command-task file parameters. For information about specifying file names. For important considerations about specifying the command-string parameter. Open the file using a text editor. see “Command-task file parameters. 5.” 3. 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.x.Windows = telnet %CMDTASK_IPV4ADDRESS0_0% For information about the parameters that you can use. Optional: Define other parameters as needed. It is your Chapter 2.

For example. create two resource-bundle files named appleResources. DescriptionKey to define a description of the task. users cannot directly type characters in their current code page for all supported languages. responsibility to ensure the accuracy of Java resource bundles that you create.properties and appleResources_es. no subsequent steps should be necessary. 194 IBMSystems Director Systems Management Guide . Italian. Note: If your translation service will translate the resource bundles you are using. National-language task titles are specified by using the Unicode or UTF8 character set. Table 14. complete the following steps: Important: You are responsible for ensuring that the data in the resource bundles is valid for the intended purpose. 1. if you created a command-task file with the file name “apple”. German. French. 2. you must create the appleResources_fr. National-language titles for English. Characters are typed in the code page in which the user is working.properties and appleResources_en. Brazilian Portuguese. and Spanish can all be typed directly in code page 850. use the keyword TitleKey to define the title. Using the translation services available to you. For each additional non-English title you must create additional resource bundles for each locale that you defined. In the properties file. 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. Create at least two properties files for resources (one default file and one English file). For example.properties. 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. The description string is displayed in the Description column on the External Application Launch page. Translators will require code page information if they are contracted to provide translated character strings. The IBM Systems Director Web interface supports the code pages listed in the following table.properties files. optionally. and. obtain translations of the title text in all the languages that you intend to support. if you provide French and Spanish titles as well. but to specify characters in another code page.

as specified in the . To configure the browser system to start an 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.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. Table 15. v The external-application task must be tested to make sure that it starts successfully on the management server. v Make sure that Java Web Start is installed 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. Using the Web interface 195 . as well as any resources required by the application. If necessary.x. Chapter 2. Copy the resource-bundle files to the applicable directory on the management server. is present on the browser system.3. 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.CMDExt file associated with the external-application task. The following prerequisites apply to this procedure: v One or more external-application tasks must be created on the management server. 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. complete the following steps: v Make sure that the application to be started by the external-application task. install the application on the browser system.

196 IBMSystems Director Systems Management Guide .” 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. click Refresh. 2. For information about the IBM Systems Director Launched Tasks program. expand Task Management and click External Application Launch. 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. The list of available external applications is refreshed. To refresh the list of external-application tasks. Note: Restarting the IBM Systems Director Server also refreshes the list of external-application tasks. In the IBM Systems Director Web interface navigation area. see “Starting the IBM Systems Director Launched Tasks program. complete the following steps: 1. On the External Application Launch page.

Then. and any resources that are required by the application must reside on the browser system from which you want to start the task. see “Authorizing users to IBM Systems Director. v When you start an external-application task. use one of the following methods. some methods might not be available. Chapter 2. For more information. expand Task Management and click External Application Launch.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.Attribute parameter. select and start an application from the External Application Launch page. you can start the task in the same ways as any other IBM Systems Director task. You can change settings by defining system attributes within the command-task file. To start the application successfully. Important: v When the external-application task is defined on the management server (the system running IBM Systems Director Server). the resulting application runs according to the settings that are present on the system where the application is started.” To start an external-application task.” v You can restrict the use of the external-application task to specific users. For information about the System. files. v Right-click a resource and select the task. the necessary applications. v In the IBM Systems Director Web interface navigation area. the task title is displayed on all instances of the IBM Systems Director Web interface. v Select the task from the Actions menu. Using the Web interface 197 . v Select the task in the IBM Systems Director Web interface navigation pane. see “Command-task file parameters. Depending on the task type.

Attention: The command-task file for the selected external-application task is permanently deleted on the management server. 198 IBMSystems Director Systems Management Guide . select one or more tasks that you want to delete. expand Task Management and click External Application Launch. In the IBM Systems Director Web interface navigation area. To delete an external-application task. complete the following steps: 1. Click Delete. 2. On the External Application Launch page. 3. The selected command-task files are deleted on the management server. They are permanently deleted. 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.

such as every Saturday at 2:00 a. Scheduler also provides automatic notification for job status and task completion.m. You can define a specific number of repeats. such as remote control and file transfer. Interactive tasks.m. 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 every Saturday at 2:00 a. You can define a schedule to repeat a task automatically at a given interval. such as inventory collection or system identification. Using the Web interface 199 . 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. for the next 6 weeks. Chapter 2. cannot be scheduled because they directly interact with only one client at a time. do not depend on immediate user input and can be scheduled to occur on multiple systems at any time.

you might have a job that is scheduled for every day at noon. 200 IBMSystems Director Systems Management Guide . Because you can run a job more than once. 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. there is a record called a job instance that represents each execution of the job. such as the Tuesday run as opposed to the Monday run. by viewing the job instance record. You could view the results for a specific execution of the job. For example. 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.

Using the Web interface 201 . For more information. see “Viewing job-instance records” and “Viewing job-instance logs. Select one or more systems or groups of systems on which you want to schedule the task to run. For more information. To schedule a task. 2.” Chapter 2. 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. click Find a Task. be aware that the group members used for the scheduled task are those members present in the group when you create this scheduled job. or copy the job. see “Noninteractive tasks. Important: Although you can select multiple target systems when you create. The changed group membership is ignored. if you schedule to collect inventory using a dynamic group and the group membership changes. Note: If you select a dynamic group. right-click a noninteractive task that you want to schedule and click Run. complete the following steps: 1. In the IBM Systems Director navigation area. Each job instance record provides detailed status information on the History page and a log file that you can view from the Log page. Subsequent changes in dynamic group membership are ignored. you can schedule one or more noninteractive tasks to run on one or more target systems. The Run window opens and the Target page is displayed. you cannot schedule it and the Run window is not displayed. For example. edit. If the task is an interactive task.” 3. the target systems originally part of the group are used for the inventory collection. On the Find a Task page. an error is logged in the job instance record. 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.

the job has errors on two systems. they are displayed on this page. the notification is not sent. Other values are Hourly. c. or Custom. a task might require setting additional parameters and the Parameters page is provided. b. Type your e-mail address. 8. 202 IBMSystems Director Systems Management Guide . In the Schedule list. a message is displayed in the Run window so that you can correct the job. Yearly. you can specify whether to run the job on the weekend. A job name is required and the Name field provides a unique default name. Daily. If the settings are blank. the Scheduler cannot save the job. If the task provides default values. Click the Notification tab. click Schedule. The job is displayed on the Active and Scheduled Jobs page. select how frequently you want the job to run. 7. Select the time range for the job to repeat. d. v When the job fails. Select whether you want the job to run according to your management server’s time or the target system’s time. Otherwise. Weekly. 6. 5. type a job name in the field. Select the date and time to run the job for the first time. you can choose to run the job immediately or schedule the job to run at a later time. b. 4. if the job runs on five systems. On this page. Rarely. e. e-mail server. Therefore. a. click Run Now and go to step 7. Click Cancel to exit from the Run window without saving the job. Tip: Make sure that you know the time and time zone to which the respective systems’ clocks are set. otherwise. and e-mail server port. If the job creation fails. 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. Also. a. On this page you can customize a notification that is sent by e-mail. and you set the criterion threshold to 50%. v When the job receives any error. a message is displayed on the page from which you started the Scheduler. Select from the available criteria to customize when the e-mail notification is sent. b. Tip: You can provide only one e-mail address. a. If the job is created successfully. To run the job immediately. 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. 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. On this page you can select additional options for the job behavior. you must enter all the settings. The default setting is Once. To change the default name. Click the Options tab. Monthly. Click OK to save the job. Click the Schedule tab. Click the Parameters tab.

To run the job immediately. To change the default name. select how frequently you want the job to run. To schedule a task from a selected system. you can choose to run the job immediately or schedule the job to run at a later time. Daily. The Run window opens and the Schedule page is displayed. Weekly. Select the date and time to run the job for the first time. A job name is required and the Name field provides a unique default name. Also. Select the time range for the job to repeat. complete the following steps: 1. 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. Using the Web interface 203 . On this page. e. Click Actions and click a noninteractive task that you want to schedule. You cannot schedule an interactive task and the Run window is not displayed. Monthly. c. Yearly. Other values are Hourly.” 3. The default setting is Once. d. 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. Chapter 2. click Schedule. In Navigate Resources or any table that displays systems. In the Schedule list. or Custom. For more information. see “Noninteractive tasks. you can specify whether to run the job on the weekend. b. type a job name in the field. v The task is an interactive task. 2. Otherwise. a. select one or more systems on which you want to perform a noninteractive task. click Run Now and go to step 7 on page 202. you can select a noninteractive task and schedule it to run on one or more systems.

If the job creation fails. a message is displayed in the Run window so that you can correct the job. If the settings are blank. 4. and e-mail server port. 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. a. Click the Options tab. 5. On this page you can customize a notification that is sent by e-mail. Select from the available criteria to customize when the e-mail notification is sent. Tip: Make sure that you know the time and time zone to which the respective systems’ clocks are set. Click the Parameters tab. You can specify that the e-mail be sent when one of the following criteria is met: v When the job begins. On this page you can select additional options for the job behavior. the notification is not sent. b. otherwise. Therefore. The job is displayed on the Active and Scheduled Jobs page. you must enter all the settings. If the task provides default values. e-mail server. a task might require setting additional parameters and the Parameters page is provided. Rarely. the job has errors on two systems. 204 IBMSystems Director Systems Management Guide . v When the job receives any error. 7. they are displayed on this page. Select whether you want the job to run according to your management server’s time or the target system’s time. Click OK to save the job. the Scheduler cannot save the job. Click the Notification tab. 6. b. a. v When the job fails. Tip: You can provide only one e-mail address. and you set the criterion threshold to 50%. a message is displayed on the page from which you started the Scheduler. Click Cancel to exit from the Run window without saving the job. if the job runs on five systems. Type your e-mail address. If the job is created successfully. 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. v When the job completes successfully.

the following information provided: Name The name of the job. including a progress indicator for each job. high-level information about active and scheduled jobs. For each job. Use this state to prevent a job from running without deleting the job. expand Task Management and click Active and Scheduled Jobs. In the IBM Systems Director navigation area. scan for the job that you want. complete the following steps: 1. To view information about active and scheduled jobs. The progress indicator is useful for tracking the progress of instances of long-running jobs. Scheduled Indicates future scheduled runs of the job and the number of systems affected by the job. Neither the job nor its history is deleted. On the Active and Scheduled Jobs page. Status The current status of the job. 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. This is a job’s initial state. 2. Inactive Indicates that the job has been disabled and scheduled instances will not be run. Running Indicates that the job is currently running and the number of Chapter 2. Using the Web interface 205 . The following list describes the available job states: Active Indicates that the job has run once and is scheduled to run again.

Next Run The date when the job will run next. a progress indicator is displayed in the column. Task The name of the task that the job runs. 206 IBMSystems Director Systems Management Guide . Progress If a job is in the Running state. not observable for some jobs. therefore. you cannot change its state to Inactive. that the job has run at least once. Description A description of when the job is scheduled to run. Complete Indicates that no future runs of the job are scheduled. affected systems. This state can be transitory and. and the number of affected systems. If a job is running. Last Run The date when the job ran most recently. Created By The user ID of the person that created 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. 3. 2. Chapter 2. On the Active and Scheduled Jobs page. expand Task Management and click Active and Scheduled Jobs. On the Properties page. the General page is displayed by default. 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. v The date that the job last ran. 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. This information includes what tasks are included in each job and. Using the Web interface 207 . when the job has run before and when it will run next. select the job that you want to view and click Actions → Properties. complete the following steps: 1. v The date that the job will run next. To view job information. v The current status of the job. if a job has a repeating schedule. In the IBM Systems Director navigation area.

3. you can perform applicable tasks on the selected job. On the Properties page. you can return to previous views using the breadcrumb links at the top of the Properties page. select the job that you want to view and click Actions → Properties. you can return to previous views using the breadcrumb links at the top of the Properties page. On the Active and Scheduled Jobs page. If you are finished viewing this information. 2. Click Actions to view the available tasks that you can perform. v The name of the job’s creator. Tip: You also can find this information by selecting a system and viewing its Properties. 4. 208 IBMSystems Director Systems Management Guide . complete the following steps: 1. click the Target tab. On the Properties page. click the Applied Activities page to view information about any jobs that are associated with the system. 4. In the IBM Systems Director navigation area. you can perform applicable tasks on the selected job. 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. If you are finished viewing this information. On this page you can view the list of target systems on which the job will run. v The name of the task that the job runs. To view the target systems. Click Actions to view the available tasks that you can perform. expand Task Management and click Active and Scheduled Jobs. Also on the Properties page. Also on the Properties page.

you cannot change its state to Inactive. On this page you can view the history of previous times that this job has run. therefore. click the History tab. On the Active and Scheduled Jobs page. In the IBM Systems Director navigation area. To view job-instance records. On the Properties page. complete the following steps: 1. Scheduled Indicates future scheduled runs of the job and the number of systems affected by the job. Inactive Indicates that the job has been disabled and scheduled instances will not be run. If a job is running. Using the Web interface 209 . including detailed information about the status of a particular instance. Neither the job nor its history is deleted. Chapter 2. This is a job’s initial state. 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. Use this state to prevent a job from running without deleting the job. 2. Running Indicates that the job is currently running and the number of affected systems. select the job that you want to view and click Actions → Properties. not observable for some jobs. expand Task Management and click Active and Scheduled Jobs. This state can be transitory and. 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. 3. A record is created for each instance of the job as soon as it starts running.

To view job-instance logs. Click Actions to view the available tasks that you can perform. In the IBM Systems Director navigation area. Skipped Indicates that a job instance did not run because a target system was offline and the number of affected systems. 4. and the number of affected systems. that the job has run at least once. Unavailable Indicates that a job instance did not run because a target system was offline and the number of affected systems. 210 IBMSystems Director Systems Management Guide . and the number of affected systems. complete the following steps: 1. expand Task Management and click Active and Scheduled Jobs. select the job that you want to view and click Actions → Properties. Failed Indicates that a job instance failed on the specified number or percentage of systems. Complete Indicates that no future runs of the job are scheduled. 2. If you are finished viewing this information. Also on the Properties page. you can perform applicable tasks on the selected job. These logs can include error messages that you can use to determine why a job instance failed. you can return to previous views using the breadcrumb links at the top of the Properties page. On the Active and Scheduled Jobs page. 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.

If the record state indicates errors. This state might be transitory and. view the log for error messages that can help you troubleshoot the problem. 4. you can return to previous views using the breadcrumb links at the top of the Properties page. On the Properties page. not observable for some job instances. Running with errors Indicates that the job instance is currently running. Also on the Properties page. Right-click a record and click Show logs. as well as one of the following status: Running Indicates that the job instance is currently running. Chapter 2. but with errors. 5. click the Logs tab. Click Actions to view the available tasks that you can perform. This state might be transitory and. Waiting with errors Indicates that the job instance is waiting for a resource to become available. On this page you can view a log for each record. but has already logged some errors. therefore. you can perform applicable tasks on the selected job. not observable for some job instances. For each job instance record. therefore. If you are finished viewing this information. The log is displayed below the table.3. Using the Web interface 211 . the page displays the date and time. but with errors. Complete Indicates that the job instance has successfully finished its execution. Waiting Indicates that the job instance is waiting for a resource to become available. Complete with errors Indicates that the job instance has finished its execution.

click OK. 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. On the Active and Scheduled Jobs page. 5. To copy a scheduled job. complete the following steps: 1. 2. When you are satisfied with your edits. select the job that you want to copy. 3. expand Task Management and click Active and Scheduled Jobs. 4. 6. The new job is saved and is displayed on the Active and Scheduled Jobs page. The Create Like window is displayed with the settings of the job that you copied. 212 IBMSystems Director Systems Management Guide . Type a new job name for this job. In the IBM Systems Director navigation area. Navigate through the Create Like window and edit the applicable job settings. Click Create Like.

The edited job is saved and is displayed on the Active and Scheduled Jobs page. expand Task Management and click Active and Scheduled Jobs. an error message is displayed stating that the job has run already and cannot be replaced. you cannot edit it. Click Edit. You can edit only jobs that have not run. Note: If the job was executed while you were editing it. 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. On the Active and Scheduled Jobs page. Chapter 2. Attention: To avoid a potential error. 2. 3. For detailed information. If this occurs. see “Scheduling a task. complete the following steps: 1. The Edit window is displayed with the job settings of the job that you want to edit. If a job has run once or more. In the IBM Systems Director navigation area. When you are satisfied with your edits. 4. Check the Next Run column to make sure the job will not run during the time you intend to edit it. Navigate through the Edit window and edit the applicable job settings.” 5. Using the Web interface 213 . the edited job is not saved. click OK. To edit a scheduled job. 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. select the job that you want to edit.

On the Active and Scheduled Jobs page. 3. therefore. complete the following steps: 1. expand Task Management and click Active and Scheduled Jobs. In the IBM Systems Director navigation area. To run a scheduled job immediately. not observable for some jobs. The Last Run column is updated also. 2. On the Active and Scheduled Jobs page in the Status column. This action does not affect any scheduled instances of the job. Click Run Now. 214 IBMSystems Director Systems Management Guide . The state might appear to change to Complete without changing to Running first. 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 state can be transitory and. the state is changed to Running. select the job that you want to run.

select the job that you want to edit. Then. In the IBM Systems Director navigation area. Click Suspend. Using the Web interface 215 . select the job and click Resume. The job is resumed. expand Task Management and click Active and Scheduled Jobs. you can resume the running of the job. it will not run any past instances that were missed during its suspension. When you want to resume the job. the state is changed from Inactive to Scheduled. 4. 2. While the job will run its future scheduled instances. To suspend and resume a scheduled job. If you suspend the job. Note: You cannot suspend a job instance that is currently running. 3. On the Active and Scheduled Jobs page. On the Active and Scheduled Jobs page in the Status column. the state is changed to Inactive. Chapter 2. A message is displayed on the page stating that the job was resumed successfully. the suspension will affect only the job instances that have yet to run. Neither the job nor its history is deleted. On the Active and Scheduled Jobs page in the Status column. 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. complete the following steps: 1.

In the IBM Systems Director navigation area. complete the following steps: 1. select one or more jobs that you want to delete. To delete a job. expand Task Management and click Active and Scheduled Jobs. 216 IBMSystems Director Systems Management Guide . The job is deleted and is no longer displayed on the Active and Scheduled Jobs page. click OK. In the confirmation window. 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. Click Delete. 3. On the Active and Scheduled Jobs page. 4. 2.

view audit log files. aomar.. the following table shows the information that makes up an audit record.44. and the status of user creation.1. CLI Command [mkgp -n cs9. Note: The last five information slots are the message field of the audit record. Consider this sample audit record from the command-line interface category: Jul 17 2007 9:04:20 AM.cs9.44. high-level actions. configuration changes. IBM Director CLI Command Failed. . important. Using the Web interface 217 . . Audit-record information Information type Example Date and time Jul 17 2007 9:04:20 AM.146. localhost.146. . 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. and delete audit log files. The contents of these slots are whatever the component requires. deletion. Use Server Auditing to enable and disable auditing on IBM Systems Director Server. Chapter 2. Using this audit record as an example. you can track what takes place on IBM Systems Director Server. Audit records The audit records provide information that is necessary to track basic. view and change the current log audit settings. Table 16. You can select from several categories of information to audit. Command line interface. The component uses the Java messageFormat routine to format the text. select which audit records to log (by choosing which categories to enable). and modification. including security.129 Group101] failed with error code [20].

message Note: This information is in a national language file that can be translated. this information type is empty and a comma delimiter is present. but not for every change that occurs.44. IBM Systems Director provides several categories of audit records. message Note: This information is in a national language file that can be translated..cs9. you will receive audit records for significant changes. System localhost. The information type is empty and a comma delimiter is present.. 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.44. Name of the class that generated the . User aomar. Name of the method that generated the . Audit-record information (continued) Information type Example Category Command line interface. IBM Director CLI Command Failed. Unused information slot . Audit record IBM Director CLI Command Failed. If it is not in the file. . audit records are logged for the running and failure of command-line interface (CLI) commands. Failure details CLI Command [mkgp -n cs9. 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.1. CLI Command [mkgp -n cs9.129 Group101] failed with error code [20]. aomar.146.cs9. Note: This slot was not used by the class that generated the message. . Table 16. this information type is empty and a comma delimiter is present.146.44.44.129 Group101] failed with error code [20].146. 218 IBMSystems Director Systems Management Guide . localhost. Note: When you select a category to audit.146.1. If it is not in the file.

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

barring other inhibitors. Manage Credentials Use the Manage Credentials page to manage all your shared credentials. 4. View the Discovery and Inventory section. v In the Common tasks area. 234 IBMSystems Director Systems Management Guide . with a user ID and password. scroll to the Discovery manager section heading and click it. Note: If a system has not been discovered. 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. The discovery manager summary for the past 30 days is displayed. 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. Systems with full access IBM Systems Director is fully authenticated and. 5. 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. – 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. access for any of those systems. 3. On the Manage tab. 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. View the Access and Authentication section. v A pie chart and corresponding list that indicate the access levels of the systems. Navigate resources Use the Navigate Resources page to view and manage discovery options on an individual resource level. 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. Systems with partial access IBM Systems Director has full access to some remote service access points for these systems but no access to others. This section provides the following information: v The number of systems that are accessible. able to perform tasks on these systems. v The number of discovered systems for which no inventory was collected. v In the Common tasks area. 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. Click any of the category list items to see a breakdown of the systems in that category. Data is obtained by using software that is already installed on the resource. it will not show up anywhere on this page.

and the dynamic elements on the page (for example. Click Discover. You also can reach the summary page by using Find a Task. To perform initial discovery. Chapter 3. systems will continue to appear after that as they respond to the discovery request and manageable objects are created. For more information. see “Finding a task. Note: You will see Discovery completed in place of the Discover button after all the discovery requests are sent. Use the associated task to perform agent-based discovery on only your local subnet and. 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. You can then use the request access tasks provided by IBM Systems Director to manually request access at a later time. After discovery is completed.” 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. The Discover Network page is displayed. the pie chart) change to reflect the current statistics of the set of discovered resources. optionally. After you install IBM Systems Director and start the IBM Systems Director Web interface for the first time. request access to the systems that are discovered. use the navigate resources task to view and work with the resources. A status icon displays the status of the system discovery. You can perform initial discovery only once for every IBM Systems Director installation. Discovering systems and collecting inventory data 235 . Click Discover. Request access later Discovers the systems but does not attempt to request access to any of them. you are presented with a Discover button on the Start tab of the Welcome page. However. Access is granted to those systems that accept the provided credentials. 3. complete the following steps: 1. 4. Launch the IBM Systems Director Web interface and click on the Start tab of the Welcome page. 2.

5. If you need to restore the default template value to the input field. Enable the application of the template to the name of each system after it is discovered by selecting Yes. Use the Run . Note: To specify hardcoded text to be inserted into the name template. 2. select All Targets to add individual resources or Groups to add group of resources. select the profile that you want to configure for automatic renaming. expand Settings and then click Auto Rename. select %TEXT%. Click Insert. IBM Systems Director assigns a name to each discovered system that might be cryptic and unsuitable. Decide which variable should be displayed first in the name of each resource and select it from the list. The Run . Click Rename. Select each subsequent variable and click Insert after each one. 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. b. Click Edit. e. 7. which contains a list of resource types and any associated rename templates. The Edit Template page is displayed. or you can configure IBM Systems Director to automatically rename each discovered system to a name that matches a specified. You can accomplish this task for each individual system in Navigate Resources. When you are finished with the Edit Template page. 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. click Reset template to defaults. click OK. On the Auto Rename page. d. 4.AutoRename page is displayed.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. which varies depending on the resource type that is selected. To automatically rename discovered systems. In the IBM Systems Director Web interface navigation area. The template that you specified will be displayed in the table. which becomes laborious when you have a large number of discovered systems. predefined template. c. 6. complete the following steps: 1. 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. 236 IBMSystems Director Systems Management Guide . is displayed. The Auto Rename page. In the Show menu. 3.

The auto rename task will either run or be scheduled to run. All the selected targets will be renamed upon execution of the task. Continue selecting targets and adding them as needed. IBM Systems Director Server attempts to communicate with target resources by using a predetermined list of protocols. click OK. 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. d. During system discovery. 8. and Common-Agent managed systems by sending a unicast request to one or more addresses. Notification Use the Notification page to choose options for an email notification that you can receive as the auto rename process progresses. Discovering systems and collecting inventory data 237 . b. Related tasks “Collecting and viewing inventory data” on page 259 System discovery To discover systems at a specific network address or range of addresses. Schedule Use the Schedule page to set the auto rename task to run immediately or at a specified time and date in the future. This method is useful in networks in which both broadcast and multicast messages are filtered. You can also schedule the task to repeat at a specified frequency.AutoRename page. Options Use the Options page to specify the time to use for the system time and how to handle unavailable systems. 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. System discovery discovers Agentless-managed systems. they are displayed in a table for viewing. When you are finished with the Run . use system discovery. Select the targets that you want to add c. To perform a system discovery. Click Add. IBM Systems Director Server sends one request to each system at a time. Platform-Agent managed systems. complete the following steps: Chapter 3. Performing a system discovery Use the System Discovery task to identify systems at a specific network address or range of addresses.

the virtual systems that are associated with that resource are also discovered. If you want to discover only a specific resource type. 2. Click Discover. 2. 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. The Processing discovery protocols message is displayed and the progress of the discovery process is displayed as a spinning graphic. click System discovery under Optional tasks. 3. As systems are discovered. Optional: If you want to stop the discovery process. If you want to discover only a specific resource type. type the IP address of the system that you want to discover. they are displayed in the Discovered Systems table. For the IP address range that contains the systems that you want to discover. In the IP address field. select it from the Select resource type list. click Stop during discovery. Click Single system (Hostname). Add a host name of a system 1. v In the IBM Systems Director Web interface navigation area. Note: After a resource is discovered. 2. System discovery methods To do this task: Complete these steps: Add a single IP address 1. If you want to discover only a specific resource type. 3. 4. select it from the Select resource type list. 1. 2. type the host name of the system that you want to discover. Add a range of IP addresses 1. Click Multiple systems (Range of IP addresses). The System Discovery page is displayed. Click Single system (IP address). select it from the Select resource type list. Select one of the following discovery methods: Table 18. 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. In the Hostname field. 238 IBMSystems Director Systems Management Guide . Open the System Discovery page using either of these two methods: v On the Welcome page. expand Inventory and then click System Discovery. 3. 3.

The System Discovery page is displayed. Discovering systems with advanced system discovery Use the Advanced System Discovery task to identify specific types of resources or to schedule a discovery task. the systems that are displayed might include additional systems that are not located at the target IP addresses or host names that you enter. v In the IBM Systems Director Web interface navigation area. 3. When discovery is completed. expand Inventory and then click System Discovery. To view the system discovery results as you discover systems. 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. As a result. 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. Open the System Discovery page using either of these two methods: v On the Welcome page. at which point it is cleared. Advanced System Discovery uses discovery profiles to manage the discovery tasks that you undertake. all the discovered systems are displayed in the Discovered Systems table. View systems as they are discovered in the Discovered Systems table. Discover systems using one of the three available methods. 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. The table will maintain the information until you exit the Systems Discovery task. Discovering systems and collecting inventory data 239 . Related tasks “Collecting and viewing inventory data” on page 259 Discovery profiles Before performing an advanced system discovery. Note: IBM Systems Director Server displays the discovery results for all discovery requests that occur on the server during your discovery request. complete the following steps: 1. 2. click System discovery under Optional tasks. including the results from other IBM Systems Director users who are accessing the same management server.

The agent can be either a Common Agent or a Platform Agent. and their subtypes: Generic system The Generic system profile type performs an SNMP-based discovery and can find any systems. 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. To discover other resources that have not been included in the configuration of an existing discovery profile. and schedule a profile to run at specific times or in response to specific events. or services not assigned a specific system type. Depending on the profile type and protocol that you choose. which are also called system types or profile types. process. devices. or delete discovery profiles. Default CIM discovery Uses the Common Information Model (CIM) configuration to discover Platform Agent resources. 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. Each discovery profile that you create corresponds to one or more types and subtypes of resources that can be discovered. BladeCenter chassis The BladeCenter chassis profile type represents BladeCenter chassis. A discovery of this type detects the management module of the chassis. run a discovery profile on specific resources. copy. if one is not discovered. you can create. You can choose from the following resource types. 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. you might need to perform any of the following tasks when creating a discovery profile: 240 IBMSystems Director Systems Management Guide . Using advanced system discovery. It will also report no agent. Default IPC discovery Uses the Interprocess Communication (IPC) configuration to discover Common Agent resources. Use the Advanced Discovery Wizard to configure or create new profiles. you can create a new profile specifically for the types of resources that you want to discover. edit. Server The Server profile type discovers a server using its service processor.

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

Optional: To prevent the Welcome page from displaying the next time you create a profile. 242 IBMSystems Director Systems Management Guide . 4. click Create. Click Next. 6. Click Next. select the type of resource that you want to discover with the profile. Select the protocols that you want to use for the discovery profile. complete the following steps: 1. On the Advanced System Discovery page. v In the IBM Systems Director Web interface navigation area. 9. Complete all pages for each protocol that you selected. Optional: If you want to provide further granularity to your discovery search. From the System type list. clear Show this Welcome page next time. 7. 11. IBM Systems Director Server uses only the communication protocols that are saved in the profile. the management server sends an IP packet for each protocol in the profile to every resource that is targeted. click Advanced System Discovery under Optional tasks. which will discover all system subtypes for the selected system type. Click Next. To create a discovery profile. you can create a discovery profile. 8. use the System subtype list to select a subtype for the system type that you previously selected. 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. Open the Advanced System Discovery page using either of these two methods: v On the Welcome page. Selecting individual agent managers In the list of agent managers. In the Profile name field. The Protocol Selection page is displayed. The Profile properties page is displayed. type a brief description for the profile. type a descriptive name for the profile. clicking Next on each page to navigate to the next page. 3. which increases network traffic. When a profile that contains multiple protocols is run. 2. select the ones that you want to use for discovery. 10. expand Inventory and then click Advanced System Discovery. In the Profile description field. The default system subtype is All. The Advanced Discovery Wizard opens and the Welcome page is displayed. The protocols that are available on the next page of the Advanced Discovery Wizard depend on which profile type is selected here. 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. 5. Note: When the profile is run. Note: The list of system subtypes is dynamically populated based on which system type you choose.

c. Directory agents c. Adding a single IP address a. For the IP address range that contains the resources that you want to discover. when discovering an IVM Therefore. Note: You cannot configure directory agents for the following profile types: v Hardware management console v Management controller v Server. Repeat this procedure until you have added all the IP addresses. Chapter 3. and then return to fill out another section and discover those other resources. Select Add a single IP address. discover those resources. Repeat this procedure until you have added all the IP addresses. When configuring CAS IP addresses. if you fill in all three sections. Importing IP addresses a. However. Adding a range of IP addresses a. d. you must fill out one section. option. Attention: All three discovery methods (unicast. ensure that you configure multicast and broadcast if you choose any of those profile types. or directory agents to discover your resources. In the Select the file that you want to import field. Unicast b. multicast and broadcast. type the IP address of the resource that you want to discover. d. b. c. Discovering systems and collecting inventory data 243 . Click Add to add the IP addresses to the list. b. 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. multicast and broadcast. Click Add to add the IP address to the list. Select Import. For example. b. Also activate or deactivate access request automation and activate or deactivate inventory discovery automation. Selecting all available agent managers Select the Use all available agent managers when this profile is run. The priority for discovery method processing is as follows: a. and directory agents) are presented on this page and you can provide information for all three at once. or you can import the addresses. Multicast and broadcast So. you can add IP addresses either individually or as a range. if you want to use multiple methods to discover resources. only one method at a time will be used to discover resources. Common Agent Services (CAS) configuration Configure either unicast. type in the name of the import file or click Browse to search for the file. only the unicast discovery is performed. Select Add a range of IP addresses. In the Single IP address or beginning range field.

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

you must fill out one section. In the Single IP address or beginning range field. Select Deactivate. 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. Click Add to add the IP address to the list. Multicast and broadcast So. Chapter 3. or directory agents to discover your resources. c. c. Repeat this procedure until you have added all the IP addresses. when discovering an IVM Therefore. b. Unicast b. Select Add a single IP address. However.use the following inventory profile. Note: You cannot configure directory agents for the following profile types: v Hardware management console v Management controller v Server. Deactivating inventory discovery automation a. Adding a single IP address a. Select Activate . When configuring CIM IP addresses. only the unicast discovery is performed. For example. Attention: All three discovery methods (unicast. Common Information Model (CIM) configuration Configure either unicast. b. The priority for discovery method processing is as follows: a. Click Add to add the IP addresses to the list. Activating inventory discovery automation a. or you can import the addresses. discover those resources. When setting inventory discovery automation. Directory agents c. Also activate or deactivate access request automation and activate or deactivate inventory discovery automation. you can choose to deactivate or activate (with an associated inventory profile) the feature. you can add IP addresses either individually or as a range. Discovering systems and collecting inventory data 245 . multicast and broadcast. Adding a range of IP addresses a. Select Add a range of IP addresses. if you want to use multiple methods to discover resources. type the IP address of the resource that you want to discover. ensure that you configure multicast and broadcast if you choose any of those profile types. multicast and broadcast. b. and then return to fill out another section and discover those other resources. and directory agents) are presented on this page and you can provide information for all three at once. In the Inventory profiles list. if you fill in all three sections. For the IP address range that contains the resources that you want to discover. only one method at a time will be used to discover resources. d. select the profile that you want to use for automatic inventory discovery.

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

Adding a range of IP addresses a. Click Add to add the IP address to the list.use the following inventory profile. you can add IP addresses either individually or as a range. Note: Ensure that the file you use is a line delimited file with one IP address on each line. activate or deactivate access request automation. or you can import the addresses. Repeat this procedure until you have added all the IP addresses. 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. d. When setting access request automation. Select Deactivate. b. In the Single IP address or beginning range field. In the Password field. Select Add a single IP address. When configuring DCOM IP addresses.use the following user login information. Select Import. d. When setting inventory discovery automation. type in the name of the import file or click Browse to search for the file. Select Activate . select the profile that you want to use for automatic inventory discovery. Repeat this procedure until you have added all the IP addresses. c. Activating access request automation a. Chapter 3. Activating access request automation a. Importing IP addresses a. you can choose to deactivate or activate (with the appropriate login information) the feature. Select Deactivate. type the password for the user ID. c.use the following user login information. Click OK to import the IP addresses. and activate or deactivate inventory discovery automation. you can choose to deactivate or activate (with an associated inventory profile) the feature. In the Select the file that you want to import field. In the Inventory profiles list. Deactivating inventory discovery automation a. b. Distributed component object model (DCOM) configuration Configure DCOM IP addresses. type a valid user ID for the resource. Adding a single IP address a. For the IP address range that contains the resources that you want to discover. Select Add a range of IP addresses. Activating inventory discovery automation a. Deactivating access request automation a. b. In the User ID field. Select Activate . b. Discovering systems and collecting inventory data 247 . Select Activate . Click Add to add the IP addresses to the list. c. b. c. type the IP address of the resource that you want to discover.

Adding a single IP address a. Select Deactivate. or you can import the addresses. Select Add a range of IP addresses. c. for example. b. Click Add to add the IP addresses to the list. Adding a range of IP addresses a. In the User ID field. c. even if you supply the correct credentials during configuration of access request automation. b. 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. Repeat this procedure until you have added all the IP addresses. you will not gain access to IPC discovered resources when the automatic access request runs. Deactivating access request automation a. In the Inventory profiles list. Select Activate . When configuring unicast. d. you can add IP addresses either individually or as a range. type the password for the user ID. Also activate or deactivate access request automation and activate or deactivate inventory discovery automation. However. Activating inventory discovery automation a. type the IP address of the resource that you want to discover. Click Add to add the IP address to the list.use the following inventory profile. select the profile that you want to use for automatic inventory discovery. so these options will not be displayed if you configure only IPC. Importing IP addresses a. For the IP address range that contains the resources that you want to discover. Instead. b. In the Single IP address or beginning range field. you can choose to deactivate or activate (with an associated inventory profile) the feature. type a valid user ID for the resource. Interprocess Communication (IPC) configuration Configure either unicast or multicast and broadcast (general or directed) to discover your resources and then optionally configure broadcast relays. if you configure IPC along with other protocols that support access request automation and inventory discovery automation. So. Note: Access request automation and inventory discovery automation are not supported on IPC. b. Select Add a single IP address. those options will be displayed but apply to only the supported protocols. Select Deactivate. 248 IBMSystems Director Systems Management Guide . When setting inventory discovery automation. Select Import. you need to request access and collect inventory manually using the tasks provided by IBM Systems Director. d. Repeat this procedure until you have added all the IP addresses. c. Deactivating inventory discovery automation a. In the Password field.

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

For the IP address range that contains the resources that you want to discover. you must fill out one section. Directory agents c. Importing IP addresses a. In the Select the file that you want to import field. Select Import. type a valid user ID for the resource. or directory agents to discover your resources. and directory agents) are presented on this page and you can provide information for all three at once. Select Deactivate.use the following user login information. multicast and broadcast. Select Activate . Select Add a range of IP addresses. only one method at a time will be used to discover resources. only the unicast discovery is performed.use the following inventory profile. Service Location Protocol (SLP) configuration Configure either unicast. type in the name of the import file or click Browse to search for the file. Adding a range of IP addresses a. 250 IBMSystems Director Systems Management Guide . Deactivating inventory discovery automation a. In the User ID field. you can choose to deactivate or activate (with an associated inventory profile) the feature. The priority for discovery method processing is as follows: a. Activating access request automation a. select the profile that you want to use for automatic inventory discovery. b. and then return to fill out another section and discover those other resources. When setting access request automation. d. if you fill in all three sections. Note: Ensure that the file you use is a line delimited file with one IP address on each line. c. you can choose to deactivate or activate (with the appropriate login information) the feature. However. In the Password field. b. type the password for the user ID. When setting inventory discovery automation. Attention: All three discovery methods (unicast. For example. b. Select Deactivate. In the Inventory profiles list. Deactivating access request automation a. Multicast and broadcast So. c. b. Click OK to import the IP addresses. discover those resources. multicast and broadcast. Unicast b. Activating inventory discovery automation a. 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. if you want to use multiple methods to discover resources. Repeat this procedure until you have added all the IP addresses. Select Activate . Click Add to add the IP addresses to the list.

specify either an IP address or a host name and set the scope. b. Enabling multicast Select Enable multicast to enable multicast. d. d. When configuring unicast. Select Add IP address. type the IP address of the directory agent that you want to discover. For the IP address range that contains the resources that you want to discover. Adding a single IP address a. b. type in the name of the import file or click Browse to search for the file. Repeat this procedure until you have added all the IP addresses. c. Click Add to add the IP address to the list. c. you can add IP addresses either individually or as a range. Click Add to add the IP address to the list. b. In the Single IP address or beginning range field.Note: You cannot configure directory agents for the following profile types: v Hardware management console v Management controller v Server. Note: Ensure that the file you use is a line delimited file with one IP address on each line. Select Add a range of IP addresses. Importing IP addresses a. In the Select the file that you want to import field. Repeat this procedure until you have added all the IP addresses. c. Setting the timeout period In the Timeout period (seconds) field. ensure that you configure multicast and broadcast if you choose any of those profile types. 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. In the IP address field. Adding a range of IP addresses a. Adding a directory agent using its IP address a. b. Click OK to import the IP addresses. or you can import the addresses. When configuring multicast and broadcast. Select Add a single IP address. Select Import. Enabling general broadcast Select Enable general broadcast to enable general broadcast. Chapter 3. Click Add to add the IP addresses to the list. Discovering systems and collecting inventory data 251 . type the IP address of the resource that you want to discover. c. When configuring directory agents. select the number of seconds that the server will wait until timing out. select to enable either and set the timeout period. when discovering an IVM Therefore.

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

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

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. Enabling multicast Select Enable multicast to enable multicast. Storage Management Initiative Specification (SMI-S) configuration Configure either a direct connection. Enabling general broadcast Select Enable general broadcast to enable general broadcast. when discovering an IVM Therefore. Choose from the following protocols: v https v http c. specify the port on which the resource listens. ensure that you configure multicast and broadcast if you choose any of those profile types. Configuring a direct connection a. Also activate or deactivate access request automation and activate or deactivate inventory discovery automation. select the type of hardware of the resource to which you want to connect. Click Edit a profile. In the IP address field. b. multicast and broadcast. Select a discovery type at the top of the page to display options for configuring that type. and port. d. Setting the timeout period In the Timeout period (seconds) field. 254 IBMSystems Director Systems Management Guide . specify either an IP address or a host name and set the scope. Click Apply. you select a hardware type. select the number of seconds that the server will wait until timing out. protocol. Modify entries in the fields as needed. Note: You cannot configure directory agents for the following profile types: v Hardware management console v Management controller v Server. IP address. specify the IPv4 IP address of the resource. In the Protocol field. When configuring a direct connection. select the protocol to use to make the connection. or a proxy using directory agents. In the Hardware type field. select to enable either and set the timeout period. When configuring a proxy using directory agents. c. In the Port field. d. When configuring multicast and broadcast.

If you want to search for directory agents with scopes other than DEFAULT. such as copying it or editing it. When setting access request automation. b. You can then select the profile to run other management tasks. or run the profile. Select Activate . you can choose to deactivate or activate (with the appropriate login information) the feature. The Summary page is displayed. Click Finish. Select Deactivate. so that is the default scope value used when searching for directory agents. When you are finished creating the profile. In the Scope field. Deactivating inventory discovery automation a. Discovering systems and collecting inventory data 255 . c. 13. In the Inventory profiles list. you can choose to deactivate or activate (with an associated inventory profile) the feature. In the Password field.use the following user login information. Click Add to add the IP address or host name to the list. Activating access request automation a. c. b. select the profile that you want to use for automatic inventory discovery. b. type a valid user ID for the resource. Click Next. 12. type the IP address or host name of the directory agent that you want to discover. type the name of a scope that you have defined. complete the following steps: a. Deactivating access request automation a. Select Deactivate. In the User ID field. Setting the scope Each directory agent is associated with a scope.use the following inventory profile. it will appear in the table on the Advanced System Discovery page. Chapter 3. Repeat this procedure until you have added all the scopes. c. In the IP address or host name field. type the password for the user ID. Click Add to add the scope to the list. A discovery request is targeted to find only those directory agents that are associated with the specified scope. Repeat this procedure until you have added all the IP addresses or host names. The directory agent shipped with IBM Systems Director has a default scope of DEFAULT. Adding a directory agent using its IP address or host name a. Activating inventory discovery automation a. Select Activate . When setting inventory discovery automation. b.

Discovery profile actions To do this task: Complete these steps: Copy an existing discovery profile 1. 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. To copy. select one of the following actions. Edit the profile properties as needed. you can copy. The Advanced System Discovery wizard is displayed. Click Finish. The profile name defaults to Copy of (original profile name). v In the IBM Systems Director Web interface navigation area. Open the Advanced System Discovery page using either of these two methods: v On the Welcome page. clicking Next to continue through the wizard. 4. but all the rest of the fields are populated with the same entries and selections as is in the original profile. or delete a discovery profile. You can also use this page to create a new discovery profile that you can then manage. 2. 2. expand Inventory and then click Advanced System Discovery. or delete a discovery profile. If you select multiple profiles. you have only the options of running them or deleting them. 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 . See “Creating a discovery profile” for instructions. you can select one or more profiles at a time. Click Create like. On the Advanced System Discovery page. Table 19. Note: When working with discovery profiles. edit. click Advanced System Discovery under Optional tasks. 3. the profile must already exist. or delete a discovery profile. Select the profile that you want to copy. complete the following steps: 1. To copy. edit. edit.

Click OK in the confirmation message box. ensure that the discovery profile that you want to use exists. Note: Any scheduled event that uses a deleted profile will continue to run until it tries to run the deleted profile. 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. Discovery profile actions (continued) To do this task: Complete these steps: Edit an existing discovery profile 1. Click Delete. Discovering systems and collecting inventory data 257 . Advanced system discovery is helpful when you want to limit your discovery using criteria that you specify. If IBM Systems Director Server successfully contacts the resource. Delete an existing discovery profile 1. Table 19. click Advanced System Discovery under Optional tasks. clicking Next to continue through the wizard. The selected profile is deleted and is no longer displayed in the table on the Advanced System Discovery page. 3. Select the profile that you want to edit. complete the following steps: 1. If the profile that you want to use does not exist. 3. Edit the profile properties as needed. Click Edit. 4. v In the IBM Systems Director Web interface navigation area. A confirmation message is displayed. 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. To perform an advanced system discovery. Chapter 3. at which point the event will fail. Open the Advanced System Discovery page using either of these two methods: v On the Welcome page. Click Finish. expand Inventory and then click Advanced System Discovery. The Advanced System Discovery wizard is displayed. you must reconfigure an existing profile for your use or create a new one. 2. Select the profile that you want to delete. it is displayed in the appropriate groups in Navigate Resources. Before performing an advanced system discovery. 2.

3. 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. click Create to start the Advanced Discovery Wizard. Click Run. a history. A discovery job is created and a message is displayed with buttons and information about the job. When discovery is completed. Use the Run . When you are finished with the Run .Advanced Systems Discovery page is displayed. progress. select one or more discovery profiles that you want to use for discovery. a list of targets. Options Use the Options page to specify the time to use for the system time and how to handle unavailable systems. Note: If the discovery profile that you want to use for the advanced system discovery does not already exist. 2.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.Advanced Systems Discovery page. On the Advanced System Discovery page. The Run . 5. and error logs. the discovered systems are displayed in Navigate Resources. click OK. 4. Note: Click Display Properties if you want to view the properties of the job. Notification Use the Notification page to choose options for an email notification that you can receive as the discovery process progresses. You can also schedule the task to repeat at a specified frequency. 258 IBMSystems Director Systems Management Guide . The Active and Scheduled Jobs page is displayed and provides information about the job including status.

firmware. software applications. that have already been discovered and collects data about the hardware and software that is currently installed on those resources. and system-contained resources. switches. and the values of those attributes by using the View Inventory option. 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. Discovering systems and collecting inventory data 259 . BIOS. 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. such as computers. or printers. and diagnostic information. 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. and virtual hardware. their attributes. operating systems. you must discover the resource using System Discovery or Advanced System Discovery and also have access to it. you can view the inventory items. network information. logical. Before you can collect inventory for a resource and view the inventory data. Chapter 3. middleware. After you collect inventory. The inventory items that are displayed include physical.

inventory attribute. Inventory value The data associated with the inventory attribute. and inventory value. Inventory profiles make it possible to collect only a subset of all available information. a description. By default. or the serial number of the physical card. These profiles are read-only. physical element model. 260 IBMSystems Director Systems Management Guide . physical element serial number. you can run an inventory collection profile on specific systems (targets). Inventory item A distinct part of a resource that makes up the whole. All Hardware Inventory This profile collects inventory from physical and virtual devices. which reduces network traffic and speeds up collection. hardware inventory. They can. You can use the existing profiles to create your own profiles by using the Create like option. and you can schedule a profile to run at specific times or in response to specific events. They cannot be deleted or edited. for example. FRU number. however. For example. 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. All Software Inventory This profile collects inventory from software resources. the attributes for a physical card might include the name. Inventory attribute The details about an inventory item. IBM Systems Director uses profiles to manage the inventory collection tasks that you create and run. Or you can create your own inventory collection profile without any preconfigured settings by using the Create option. or software inventory. Inventory data comprises three parts: inventory item. the date it was last changed. physical element manufacturer. Note: The All Inventory profile is the one you must run if you intend to use update manager. hardware inventory might include a physical card as an inventory item. Software Images Discovery This profile collects inventory from software images. Using IBM Systems Director Web interface. The inventory item might fall into the following categories: basic system information. and more. 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. for example. Basic System Information This profile collects inventory from system resources. the name of a physical card. manufacturer date. be copied.

Click Next. In the Timeout period field. 14. The Options page is displayed. 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. Click Next. Pages for each of the discovery modules that you selected are displayed. Note: You can add an entire group of resource types or you can select them individually. The timeout value indicates the length of time to wait for a response to inventory collection communications that are sent to systems. 12. The View and Collect Inventory page is displayed. 11. optionally type a brief description for the profile. Click Next. Click Next. Click Add. 3. To create an inventory collection profile. v In the IBM Systems Director Web interface navigation area. Discovering systems and collecting inventory data 261 . 9. Continue adding resource types to the profile as needed. 16. type the number of minutes that you want to allot before an inventory collection event terminates. the Module Selection page is displayed. Select the discovery modules that you want to configure to discover additional attributes on your resources. The Inventory Selection page displays a hierarchical tree of the types of resources for which IBM Systems Director can collect inventory. 15. 17. If you do not want to use one of the profiles that is shipped with IBM Systems Director. Click Manage Profiles. skip right to the steps about the Options page. type a descriptive name to identify the profile. Navigate to and select the group or resource type that you want to add. Complete the pages for each discovery module. The Manage Inventory Profiles page is displayed. Open the View and Collect Inventory page using either of these two methods: v On the Welcome page. In the Profile Description field. 8. Click Create. expand Inventory and then click View and Collect Inventory. Note: If you selected Let the system choose the discovery services. 7. If the timeout Chapter 3. 4. 6. select the inventory collection profile that you want to use. In the Profile Name field. click Collect and view inventory under Optional tasks. Click Next. Related concepts “Update manager” on page 12 Creating an inventory collection profile Use the Create Inventory Profile wizard to create an inventory collection profile. The Create Inventory Profile wizard opens. 5. 2. From the Inventory Collection Profile list. If you selected Let me manually configure the discovery services. The Discovery Service page is displayed. you must create and configure a profile that meets your needs before collecting or viewing inventory. complete the following steps: 1. 13. 10. listing the existing inventory collection profiles.

20. expand Inventory and then click View and Collect Inventory. If you select multiple profiles. you have only the options of running them or deleting them. value elapses before the response is received from the destination no inventory data will be collected from that target. you can run it by clicking Collect Inventory. Click Next. select Retry failed agents. The Summary page is displayed. or delete an inventory collection profile. See “Creating an inventory collection profile” for instructions. or delete inventory collection profiles. select one of the following actions. specify the lowest possible number of agents. 19. complete the following steps: 1. the profile must already exist. 262 IBMSystems Director Systems Management Guide . 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. Click Manage Profiles. You can also use this page to create a new inventory collection profile that you can then manage. v In the IBM Systems Director Web interface navigation area. After creating an inventory collection profile. listing the existing inventory collection profiles. Open the View and Collect Inventory page using either of these two methods: v On the Welcome page. 21. Note: When working with inventory collection profiles. The View and Collect Inventory page is displayed. To copy. 2. click Collect and view inventory under Optional tasks. On the Manage Inventory Profiles page. 18. edit. 3. edit. you can select one or more profiles at a time. edit. In the Maximum simultaneous collections field. The Manage Inventory Profiles page is displayed. or delete an inventory collection profile. To copy. To instruct IBM Systems Director Server to automatically retry failed collection attempts. Click Finish. type the maximum number of agents from which IBM Systems Director Server can simultaneously collect inventory. Note: To help reduce network traffic.

3. Table 20. The new profile based on the original profile will appear in the table on the View and Collect Inventory page. Click Delete. If the inventory collection profile does not exist for the type of inventory data you want to collect. Click Create like. 3. Chapter 3. 2. Select the profile that you want to copy. 3. The selected profile is deleted and is no longer displayed in the table on the View and Collect Inventory page. Select the profile that you want to edit. 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. Edit an existing inventory collection profile 1. 2. The Edit Inventory Profile wizard is displayed. Click Finish. Discovering systems and collecting inventory data 263 . you must first create the inventory collection profile and make sure that it contains the appropriate settings. 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. you must discover that resource using System Discovery or Advanced System Discovery. Delete an existing inventory collection 1. A confirmation message is displayed. Click OK in the confirmation message box. Select the profile that you want to delete. Edit the profile properties as needed. clicking Next to continue through the wizard. The Create Like Inventory Profile wizard is displayed. clicking Next to continue through the wizard. Inventory collection uses inventory collection profiles. Click Edit. 4. Before you can view inventory for a resource. profile 2. 4. Inventory collection profile actions To do this task: Complete these steps: Copy an existing inventory collection profile 1. Edit the profile properties as needed. You can use an existing profile to collect inventory for a system. 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. Click Finish.

When inventory collection is completed. In the Target Systems list. Click OK. select the system for which you want to view or collect inventory data. The Run . e. Use the Run . a. You can also schedule the task to repeat at a specified frequency. Note: Click Display Properties if you want to view the properties of the job. d. Select one or more target systems that you want to add. drill down to the individual target system for which you want to view inventory data in the group that contains that target system. 4. Click Browse to open the Context Chooser. To change the access state. The Active and Scheduled Jobs page is displayed and provides information about the job including status. complete the following steps to add the system to the list. The Context Chooser displays a list of system groups. 5. c. 6. 2. If the target system that you want to view is not in the target systems list. b.Collect Inventory page is displayed. and error logs. progress. you can view the inventory data list and table by clicking View Inventory. When you are finished with the Run . Open the View and Collect Inventory page using either of these two methods: v On the Welcome page. click OK. In the list of groups.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. To collect inventory for one or more systems. click Collect and view inventory under Optional tasks. An inventory collection job is created and a message is displayed with buttons and information about the job. Click Add. v In the IBM Systems Director Web interface navigation area. 3. expand Inventory and then click View and Collect Inventory. Options Use the Options tab to specify the time to use for the system time and how to handle unavailable systems. complete the following steps: 1. Notification Use the Notification tab to choose options for an email notification that you can receive as the inventory collection process progresses. In the Manage inventory profiles list. The selected target systems are displayed in the Selected list. Click Collect Inventory. a history. The View and Collect Inventory page is displayed. select the inventory profile that you want to use. Note: You can select the entire group or you can drill down to select individual target systems as targets within a group. 264 IBMSystems Director Systems Management Guide . select the system or systems and click Actions → Request Access.Collect Inventory page. Note: Inventory is displayed for only those systems that are in a state other than no access. a list of targets.

and system-contained resources. Chapter 3. BIOS. In the Manage inventory profiles list. Click OK. firmware. and diagnostic information. e. click Collect and view inventory under Optional tasks. complete the following steps to add the system to the list. a. Click Browse to open the Context Chooser. select the system or systems and click Actions → Request Access. The View and Collect Inventory page is displayed. expand Inventory and then click View and Collect Inventory. The inventory that is displayed includes physical. The selected target systems are displayed in the Selected list. To change the access state. b. If the target system that you want to view is not in the target systems list. v In the IBM Systems Director Web interface navigation area. Note: You can select the entire group or you can drill down to select individual target systems as targets within a group. To display inventory data for a resource. you must collect the inventory data for that resource. Open the View and Collect Inventory page using either of these two methods: v On the Welcome page. Also. drill down to the individual target system for which you want to view inventory data in the group that contains that target system. software applications. select the inventory profile that you want to use. The Context Chooser displays a list of system groups. Before you can view inventory data for a resource. select the system for which you want to view or collect inventory data. Note: Inventory is displayed for only those systems that are in a state other than no access. c. operating systems. middleware. IBM Systems Director displays the inventory data for the inventory items that are collected. Select one or more target systems that you want to add. logical. 3. In the list of groups. Click Add. In the Target Systems list. d. and virtual hardware. 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. 2. network information. complete the following steps: 1. Discovering systems and collecting inventory data 265 .

The inventory data for the selected resource is displayed. an empty table is displayed and the Last collected value will be none. 4. Note: If you click View Inventory before any inventory has been collected by IBM Systems Director Server. 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 . make sure that you discover the applicable resources and collect the inventory for them. Click View Inventory. Before you try to view inventory.

As an example. 1999. Changes can be made if necessary. You can deploy a configuration template on a system even if it is not a member of a configuration plan. Configuration settings for a whole system can be stored as a set of configuration templates. delete. view. All specific configuration settings are described in the documentation for their specific devices. The configuration settings for storage devices are described in the IBM Systems Director Storage Systems documentation. You also can create configuration settings from scratch. the configuration settings for IBM BladeCenter and System x are described in the documentation for IBM BladeCenter and System x. deploy. Configuration plan A set of configuration templates used to configure a system. and schedule configuration templates to be deployed on a target resource. which can be saved as a configuration template or as a configuration plan. and the configuration setting for an individual resource can be stored as a configuration template or as a configuration plan. Configuration templates A configuration template is a stored version of device parameters and settings. edit. but are stored for future deployment. You can save configuration settings from a system and convert them into configuration templates or configuration plans. such as login information or SNMP options. you can configure both hardware devices and systems so that they will wor