Deleting cluster configuration  ------------------------------------------------------------------------- 0.40s cli-base : Delete Bridge Network  https://9.16.27.18/api/com.ibm.zBlockchain/networks/aaa_vlan00b90_2309_proxy_network  ------------------------------------------------------------------- 0.38s cli-base : LPAR API token https://9.16.27.18/api/com.ibm.zaci.system/api-tokens  ------------------------------------------------------------------------- 0.35s Pre-UnInstallation Operations  ----------------------------------------------------------------- 0.12s Generate peer configuration  ------------------------------------------------------------------ 0.11s Update Peer configuration with master IP and IPSec shared key  ------------------------------------------------------------------------- 0.10s Set container configuration  ------------------------------------------------------------------------- 0.10s configuration : Checking container template  ------------------------------------------------------------------------- 0.10s Delete containers for Templates  ------------------------------------------------------------------------- 0.09s Delete containers for Templates  ------------------------------------------------------------------------- 0.09s Figure 3-19 Output of the SSC uninstaller Creating the containers in your SSC partition Note:  Before you proceed with these steps, ensure that the internal IP address  ( 192.168.0.251 ) is configured on the IBM Z master node server. You might want to use  ip  addr show  command. On the Linux on Z master node server, complete the following steps as a root user. 1. Run the command line tool to create the cluster nodes. Notice that the command must be  run in the parent directory of the  config  directory, for example,  /opt/blockchain . See  Example 3-30. Example 3-30 Installing the SSC containers docker run --network=host --rm -it -v $(pwd)/config:/ssc4icp-cli-installer/config  ibmzcontainers/ssc4icp-cli-installer:1.1.0.3 install The following  cluster-configuration.yaml  example file is generated based on the cluster  configuration that is specified in the ssc4icp-config.yaml  file. Notice that new containers  were created ( 192.168.0.245 ,  192.168.0.246 , and  192/168.0.247 ). 2. Check the yaml files under config/DemoCluster/: Example 3-31 Sample of cluster-configuration.yaml file LPARS: - containers: - cpu: '2' icp_storage: 40000M internal_network: gateway: 192.168.0.1 ip: 192.168.0.253 parent: encb53 subnet: 192.168.0.0/24 Chapter 3. Secure Service Container installation and configuration  109