self-describing agent - user controls...tivoli sapm ibm confidential itm self-describing agent: user...
TRANSCRIPT
© 2009 IBM Corporation
IBM Tivoli Monitoring 6.3.0 Pre-Beta Demo
Self-Describing Agent - User Controls Date: 7/17/2012 (RTC EPIC 17265 )
Tivoli SAPM
Confidential
Tivoli SAPM
IBM Confidential
Tivoli SAPM
IBM Confidential
ITM Self-Describing Agent: User Control
New for ITM 6.3.0
Control which product support is automatically
installed on the servers by SDA.
Dynamically configure specific ITM products &
versions to “allow” SDA to install.
Dynamically enable and disable all SDA
operations for the ITM Enterprise
No recycling of the HUB Monitoring Server.
Tivoli SAPM
IBM Confidential
ITM Self-Describing Agent: User Control
New SDA configuration settings stored and
managed at HUB Monitoring Server Database.
For SDA installs, the HUB controls all ITM
Enterprise operations.
Configurations do NOT apply separately to
specific RTEMS.
– Managing different settings at each RTEMS is much
more complex (may possibly be considered in the
future).
Tivoli SAPM
IBM Confidential
Tivoli Monitoring
© 2011 IBM Corporation 6
New ITM 6.3.0 SDA Admin tacmds
Display SDA enablement status of ALL Monitoring
Servers
Indicate when SDA Operation is Suspended
tacmd suspendsda
Suspend or halt all SDA function for the ITM Monitoring
Servers.
Recommend issuing before config changes
tacmd resumesda
tacmd listsdastatus
Resume or restore SDA functions for the ITM
Monitoring Servers.
Issue after config changes are all made.
Tivoli SAPM
IBM Confidential
tacmd suspendsda & resumesda
Dynamically suspend (disable) or resume
(enable) SDA service for the ITM Enterprise
Provides control over when SDA installs occur
More safety when making configuration
changes
Running Agents are notified to SDA Register
again when SDA service is resumed.
Tivoli SAPM
IBM Confidential
tacmd listsdastatus
For 6.2.3, the Monitoring Server SDA
operational status display was in:
– tacmd listappinstallrecs
For 6.3.0, tacmd listappinstallrecs
– no longer shows these records
– only shows SDA product installation status
Now SDA operational status only displayed by:
– tacmd listsdastatus
Tivoli Monitoring
© 2011 IBM Corporation 9
Example of listsdastatus
Indicates when SDA Operation is Suspended
Shows Operational Status of Monitoring Servers
Tivoli Monitoring
© 2011 IBM Corporation 10
New ITM 6.3.0 SDA Admin tacmds
Remove a specific version configuration
remove all versions for a product
Display existing SDA product install configurations from
the Hub TEMS
tacmd addsdainstalloptions
Configure specific product(s) and version(s) to
allow SDA to install.
tacmd editsdainstalloptions
tacmd deletesdainstalloptions
tacmd listsdainstalloptions
Modify an existing product version configuration
Change the DEFAULT SDA install behavior (ON,OFF)
Tivoli SAPM
IBM Confidential
SDA Product Version Configuration
ITM 6.2.3 release only allows an administrator to configure
all SDA as ON or OFF for:
– the entire ITM enterprise, or
– specific TEMS or TEPS server at server startup time.
ITM 6.3.0 provides dynamic configuration of specific ITM
products & versions via tacmd CLI for SDA install.
All products and versions not configured would be
prevented or blocked from SDA installation.
Most ITM customers will not adopt SDA automatic TEMS and
TEPS installation without more control over what products
get installed and when they get installed.
Tivoli Monitoring
© 2011 IBM Corporation 12
6.3.0 SDA Default Behavior Change
To provide added safety for 6.3.0 SDA adopters
– that SDA installs would not automatically occur once
SDA for the HUB TEMS is switched on.
6.2.3 TEMS: if SDA is on (KMS_SDA=Y)
– All running agents products installed based on latest
version.
After upgrade to 6.3.0, HUB TEMS will block all products
and versions from SDA install until:
– specific product versions are configured via tacmd
– or run this tacmd to return to 6.2.3 SDA behavior:
– tacmd editsdainstalloptions -t default -i ON
Tivoli Monitoring
© 2011 IBM Corporation 13
6.3.0 SDA Default Behavior Change
Special Consideration for z/OS HUB TEMS during
upgrade from 6.2.3 to 6.3.0
Avoids tacmd CLI to revert back to 6.2.3 behavior
z/OS ICAT Configuration Program will provide
special handling
If z/OS HUB was previously configured for SDA use
(with KMS_SDA=Y)
SDA behavior automatically reverts back to 6.2.3x
as if this tacmd command was run by the user:
tacmd editsdainstalloptions -t DEFAULT -i ON
Tivoli SAPM
IBM Confidential
Configuration of Multiple Versions
Many different product versions can be configured
We expect administrators would eventually remove existing
configurations that are old or obsolete.
SDA Install configuration records reside only on the HUB
TEMS and not at the RTEMS.
All SDA configured product versions apply to the entire ITM
Enterprise (all RTEMS, TEPS, etc)
Specific RTEMS or TEPS servers can not be individually
configured for SDA product versions.
TEMS notifies running SDA agents to retry their SDA
registration when a new product version configuration is
– added (tacmd addsdainstalloptions) or
– updated (tacmd editsdainstalloptions).
Tivoli Monitoring
© 2011 IBM Corporation 15
You may need to allow multiple versions because SDA does not
update each RTEMS with the latest version that is at the Hub.
Instead SDA updates the RTEMS with the latest version of app
support for its connected agents
Why you may need to allow SDA for multiple versions
HUB
TEMS
RTEMS 1 RTEMS 2
FP3 FP3 FP2 FP2 FP2 FP2
Tivoli Monitoring
© 2011 IBM Corporation 16
Example of listsdainstalloptions
Indicates default SDA install control
– When default is OFF, all product installs BLOCKED unless
configured
Shows Product Versions configured for SDA
Tivoli Monitoring
© 2011 IBM Corporation 17
SDA Configuration Audit Messages
HUB TEMS uses ITM Audit and MSG2 messages to
track any HUB DB changes for:
– suspend or resume mode
– install configuration settings
– product seeding configuration settings
Includes tacmd user id and address
Fri May 18 15:32:10 2012 KFASD109 Self-Describing Agent User Configuration Record
Insert by UserID <sysadmin> at <194.56.112.23> for GRPID <5530> PRODUCT <LZ> ID
<INSTALL> CONFIG <VER=06300000;I_VER=06300000-06300000;>.
Fri May 18 15:32:10 2012 KFASD109 Self-Describing Agent User Configuration Record
Update by UserID <admin01> at <194.56.112.23> for GRPID <5530> PRODUCT <TEMS> ID
<SUSPEND> CONFIG <SDA_SUSPEND=YES;>.
Fri May 18 15:32:20 2012 KFASD109 Self-Describing Agent User Configuration Record
Insert by UserID <admin02> at <9.52.118.76> for GRPID <5530> PRODUCT <NT> ID
<SEEDDIST> CONFIG <INSTALL=NEW;UPGRADE=NONE;>.
Tivoli SAPM
IBM Confidential
Remote TEMS Config Notifications
Ensure the Remote TEMS will notify all running SDA
agents that they can retry their SDA install, if needed.
Provides HUB and RTEMS sync of SDA TAPPLPROPS
table Configuration Records when RTEMS reconnects.
For SDA user config records modified by:
– tacmd *sdainstalloptions (add, edit, delete)
– tacmd suspendsda
– tacmd resumesda
For example, if RTEMS was disconnected from HUB:
– You want all available agents to retry SDA,
– issue tacmd suspendsda, then tacmd resumesda
– RTEMS detects this user request when it reconnects to the
HUB.
© 2011 IBM
Corporation
Questions & Answers
Tivoli SAPM
IBM Confidential
Rational Team Concert References
EPIC 17265 - Desc: As an ITM administrator, I want to control which agents
and versions can be enabled or disabled for self-description so that I can
control how sda support is propagated to my TEMS and TEPS production
environment.
User Story 17831 - Desc: As a TEMS administrator, I want to use tacmd
commands to specify and view the agent version(s) that are allowed to perform
SDA so that SDA only occurs for agent versions that have been certified for use
in my environment
User Story 18876 - Desc: As an ITM administrator, I want the RTEMS to
notify all allowed agents that they can perform SDA if SDA install changes
occurred while the RTEMS was disconnected from the Hub so that my config
changes are honored once the RTEMs reconnects.
Tivoli SAPM
IBM Confidential
RTC References
User Story 16234 – Desc: As an ITM Administrator, I want to list whether
SDA is enabled for each of my TEMS using its own tacmd list*sda, so that I can
see all TEMS SDA status entries separate from other HUB TEMS only user
configuration options.
User Story 22485 - Desc: As an ITM Administrator, I want to execute the
CLI tacmd suspendsda and resumesda to dynamically disable and re-enable
SDA operations for the ITM Enterprise.
User Story 17990 - Desc: As ITM Administrators, I want audit records for
SDA configuration setting changes to include the userid so that I can know who
made changes.
Tivoli SAPM
IBM Confidential
RTC References
User Story 20231 – Desc: As an adminstrator, I do not want the tacmd
listappinstallrecs command to display SDA config settings or TEMS SDA Status
(i.e. 5530 records) since these settings and status should be displayed by other
tacmd that can properly format the display.
User Story 20231 – Desc: US - As an adminstrator, I do not want the tacmd
listappinstallrecs command to display SDA config settings or TEMS SDA Status
(i.e. 5530 records) since these settings and status should be displayed by other
tacmd that can properly format the display.
User Story 27310 – Desc: US - As an ITM Administrator, the new 6.3.0 SDA
tacmds should issue warning messages if any on-line down-level RTEMS will
have problems with the command.