Initializing the system with the technician port (IBM® SSR task)

To initialize the system, connect a computer to a technician port of the node canister by using an Ethernet cable, and then open a wizard in a supported web browser.

Before you begin

View the Planning worksheets.

Note: If you are unable to connect to the system through the technician port, you can use the service assistant tool or the service CLI to initialize the system. Complete the following steps.
  1. Access the command line by using the superuser credentials.
  2. Enter the following CLI command to create the system: 
    mkcluster -clusterip x.x.x.x -mask m.m.m.m -gw g.g.g.g -name name

Procedure

  1. Ensure the system is powered on.
  2. Configure an Ethernet port on the personal computer to enable Dynamic Host Configuration Protocol (DHCP) configuration of its IP address and DNS settings.

    If you do not have DHCP, you must manually configure the personal computer. Specify the static IPv4 address 192.168.0.2, subnet mask 255.255.255.0, gateway 192.168.0.1, and DNS 192.168.0.1.

  3. Locate the technician port on each node canister, as shown in the following figure:

    The technician port is labeled with the "gear" icon.

    Figure 1. Technician port
    Technician ports
    •  1  Node canister 1 technician port
    •  2  Node canister 2 technician port
  4. Disconnect the personal computer from all networks. Connect an Ethernet cable between the port of the personal computer that is configured in step 2 and the technician port in the left canister (1) that is shown in Figure 1.
  5. After the Ethernet port of the personal computer is connected, open a supported browser and browse to address https://install. (If you do not have DCHP, open a supported browser and go to the following static IP address 192.168.0.1.)
    The browser is automatically directed to the initialization tool.
  6. Follow the instructions that are presented by the initialization wizard to configure the system with a management IP address.
  7. After you complete the initialization process, disconnect the cable between the personal computer and the technician port. Continue to initial system setup, see Completing the initial system setup (customer task).
  8. If the node canisters communicate with each other by using RDMA over Ethernet, then browse to address https://install and press the wrench icon on the initialization page to access the Service Assistant Tool. Use the Change node IP tab of the Service Assistant Tool to configure the node IP settings for the node as provided by the customer on the worksheet. Repeat this step for each node canister that is in the system.
  9. Using the initialization GUI, enter the requested information by using the worksheets that you created during the planning phase, including the management IP address, subnet mask, and gateway.

What to do next

Important:
  • Connect to the system CLI using SSH and use sainfo lsrootcertificate and satask exportrootcertificate to export the system's root certificate and add it to the browser's trust store. The root certificate must be exported from the node that will be used to initialize the system.
  • Browser security features might alert the user that the system certificate does not contain a valid subject alternative name. It is safe to accept the risk and continue. A new certificate that contains a valid subject alternative name can be created after completing system initialization. See System Certificates for instructions to create a new certificate.
  • It might be necessary to remove old certificates that are stored in the browser before the browser accepts the request.
  • The web browser might display a warning about a potential security risk if the root certificate is not added to the browser truststore. It is safe to accept the risk and continue.
  • After the technician port physical connection is completed (that is, connected both ends), it can take up to 45 seconds before the port is fully up and able to process requests. Submitting requests before this interval might result in 404 error responses.
  • If the https://service request in the browser causes a 404 error, or fails to produce a response, it might be necessary to use the url https://192.168.0.1 in the browser request to connect to the system.