Note: The -gateway, -primary, and -secondary parameters set the default gateway and DSN servers for all TCT network connections of a DS8000 internal server. You can have only one gateway and one set of DNS servers. Therefore, routing into different networks is not possible. All cloud targets must either be accessible through the local subnet or a single gateway. It is possible to route each internal server’s connection through different subnets if each server can access all cloud targets.

Note: Network ports cannot be created or deleted. The only way to unconfigure a port is to clear the configured IP address by setting it to “0.0.0.0”.

Note: You can have up to six Ethernet ports available in each DS8000 internal server. It is a best practice to use only ports of the same type, for example only the 10 Gbps ports, to avoid performance imbalance. For more information about networking requirements, see Chapter 5, “Connectivity and network setup for Transparent Cloud Tiering” on page 45.

Important: Since Release 9.2, the DS8900F supports up to eight independent cloud connections. Since this release, the way these connections are managed has changed: •If you define only one connection, everything works as before. All commands (create or delete connection) have an immediate effect. •As soon as you define more than one connection, any modification to the cloud connections requires an extra activation step. This step is disruptive to ongoing TCT operations. It removes and re-creates all defined cloud connections. Active TCT data transfers are terminated and must be restarted by the application that initiated them. For more information and examples, see 6.3, “Managing multiple cloud connections” on page 60.

Note: TCT secure data transfer with TS7700 is supported for DS8900F R 9.1 and later. For prior releases, the -nossl option is required for TS7700 as object storage target.

Note: If you use TCT secure data transfer with TS7700, you must provide certificates only if you changed the TS7700 secure data transfer certificate. The DS8900F knows and accepts the factory-provided certificates of the TS7700.

Note: Anybody with access to the cloud credentials you use to connect a DS8000 to cloud storage has full access to all objects TCT stores in the cloud, including the capability to update, move, or delete data. Make sure that you treat these credentials with the appropriate care.

Note: In our example, we specified the IP address of one accessor node of the IBM Cloud Object Storage, which is a single point of failure. For a production configuration, you would either provide the IP address of a load balancer that has access to several accessor nodes, or the virtual address of an accessor node pool.

Note: Before you can use TCT encryption, you must configure your IBM Security Key Lifecycle Manager servers and DS8000 encryption settings (key server and key group) according to IBM DS8000 Encryption for Data at Rest, Transparent Cloud Tiering, and Endpoint Security (DS8000 Release 9.2), REDP-4500.

Note: If you want to use SSL for secure authentication with the IBM cloud, you can download the endpoint security certificate (for example, by using the openssl command). Then, provide the certificate file in the syscaloc parameter of the mkcloudserver command.

Additional information: For more information, see IBM TS7700 Series DS8000 Object Store User's Guide Version 2.0, REDP-5583. This publication is not updated yet to cover the changes that were introduced with TS7700 release 5.22 and FC 5283.

Note: With DS8900F R 9.1 and later, TCT supports compression with TS7700 as object storage. Compression is enabled or disabled in z/OS. You enable TCT compression in z/OS, as described in 7.5, “Enabling TCT compression with a TS7700” on page 77. You do not need to configure anything in the DS8900F or TS7700 to use TCT compression.

Note: You can specify up to four IP addresses for each TS7700. Only one link is used at a time. The others are for redundancy. Only IPv4 is supported.

Note: If you remove all connections except the last one from a multi-cloud configuration, the configuration turns into a single-cloud configuration.

Note: A managecloudserver -aplypndconfig command is disruptive to ongoing TCT operations. It removes and re-creates all defined cloud connections. Active TCT data transfers are terminated.

Note: A major use case for multiple DS8000 cloud connections is the selection of TS7700 object policies. Using the TS7700 user interface, you can define policies for stored objects that specify where in the TS7700 grid objects are stored and how they are replicated. To call such a policy, you must define a DS8000 cloud connection to the TS7700 grid and name it like the policy that you want to use. If you have more than one object policy, you define a DS8000 cloud connection for each of them.

Attention: The user ID that is created for the DFSMS to connect to the DS8000 follows the security rules that are defined in the Authentication Policy of the DS8000. Therefore, depending on your policy rules, this password can expire after a certain number of days. To avoid connectivity issues with TCT, change the password of this user ID both in the DS8000 and the DFSMShsm before the expiration date, or modify the expiration date policy to never expire.