1. IBM Tivoli Provisioning Manager 7.1.1 IPv6 Enablement
IBM Software Group | Tivoli Brand Software
IBM Tivoli Provisioning Manager IPv6 Enablement
IBM Tivoli Monitoring for Transaction Performance v52 ESP Workshop Workshop Guide

2. Topics Feature Objective (Problems Solved) Feature Overview
Common Use Cases

3. TPM 7.1.1 IPv6 Enablement Objective
Enable TPM to be IPv6 enabled

4. Topics Feature Objective (Problems Solved) Feature Overview
Common Use Cases

5. IPv6 Enablement in TPM 7.1.1: TPM Server
TCP/UDP PI
Server
IPV4
x.y.z.w
a:b:c:d:e:f:g:h
IPV6
TPM
TCA
A dual stack (IPv4 and IPv6 enabled) TPM server is required for communication over IPv6
IPv6 DOES NOT NEED TO BE ENABLED AT TPM SERVER INSTALLATION TIME
A property update can be used to enable post-installation

6. IPv6 Enablement in TPM 7.1.1: SDI
TCP/UDP PI
Server
IPV4
x.y.z.w
a:b:c:d:e:f:g:h
IPV6
TPM
TCA
A variety of SDI configurations are possible (common agent and depots):
IPv4 only, IPv6 only, dual stack (IPv4 and IPv6)
DNS must be enabled for the TCA for IPv6 flows to be operational
Once enabled, all SDI-based scenarios are supported over IPv6

7. IPv6 Enablement in TPM 7.1.1: DE
TCP/UDP PI
Server
IPV4
x.y.z.w
a:b:c:d:e:f:g:h
IPV6
TPM
TCA
Four specific Deployment Engine scenarios are supported over IPv6:
Network Discovery
Inventory Discovery
Windows Patch
Agent Install

8. IPv6 Enablement in TPM 7.1.1: Discovery
TCP/UDP PI
Server
IPV4
x.y.z.w
a:b:c:d:e:f:g:h
IPV6
TPM
TCA X
When the IPv6 property is enabled, you may discover and view IPv6 information in the TPM UI
IPv6 network support does not have to be enabled for the TPM server to discover IPv6
You may choose whether you want to discover and manage IPv6 targets, or additionally exploit IPv6 for communication, with no need to choose at installation time

9. Topics Feature Objective (Problems Solved) Feature Overview
Common Use Cases

10. BACK UPS

11. IPv6 Background
IPv6 is an industry standard for the IP network. It removes the IP addressing limitation of IPv4, and provides more quality of service and IP security. It is also a key requirement from the U.S. Federal Government who has mandated that all software products to be considered for US government projects must support IPv6 by June 30, To comply with this requirement, a product must work normally, with full function parity, over IPv6 on the supported platforms. Additionally, the product must provide "dual-stack" support. This means that the product must be able to communicate using both IPv4 and IPv6 protocols simultaneously with other applications using IPv4 or IPv6. In a "dual-stack" environment, the device supports both IPv4 and IPv6 and the proper protocol (i.e. IPv4 or IPv6) will be selected at run time on a case-by-case basis depending on whether the remote peer also supports IPv6, has IPv6 connectivity, and has advertised a desire to use IPv6 via the DNS. Naturally, IPv4 continues to work as expected when used. This allows customers to stage the transition from an IPv4 environment to a complete IPv6 environment

12. IPv6 Background (cont)
IPv4 addresses are 32 bits long; IPv6 addresses are 128 bits long. e.g. 2001:0db8:85a3:0000:0000:8a2e:0370:7334
IPv4 addresses use “.” as separator; IPv6 addresses uses “:” as separator and can also in addition use “.” as separator. IPv4 address strings can fit in 15 characters; IPv6 requires 39 characters.
IPv4 subnets tend to be densely populated; IPv6 subnets will be sparsely populated as most subnets can have 2^64 hosts. Scan of address ranges should be restricted to complete in a reasonable time. The recommendation for restriction is an interval on the order of hundreds of addresses with detection at data entry time.
DNS lookup of a host can return both IPv4 and IPv6 address.
In IPv4 hosts can reach other hosts via IPv4; since IPv6 networks will be sparse, some IPv6 traffic will have to traverse IPv4 networks.
In HTTP addresses ":" is used to separate address and port fields. IPv6 addresses use ":" as a delimiter, so the entire IPv6 address is quoted by enclosing it between "[" and "]"

13. Limitations The TPM server must be a dual stack implementation.
All communication between TPM managed-from components (DB2, WAS, CAS, DCD, etc.) will be via IPv4.
The TPM installation and migration utility will set up the infrastructure for IPv6 enablement but will not enable IPv6 support explicitly.
All SDI IP-based configuration will continue to use IPv4 based addresses.
The hostname for the TPM server should be configured in DNS to return both the IPv6 and IPv4 address.
The hostname for the TPM server should be configured for the same domain for both the IPv6 and IPv4 address.
Windows support is limited (dependency on Cygwin 1.7).
IPv6-specific scenarios will not be supported for the TPM policy engine, firewall proxy, router, and ACL management functions.
HADR implementations based on a service IP will require specific IPv6 support from the cluster manager.
TPMfOSD will not have support for IPv6.