To initialize the system, connect a computer to a technician port of the node by using an Ethernet cable, and then open a wizard in a supported
web browser.
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.
Locate the technician port on the node, as shown in the following figure:
The technician port is labeled with the "gear" icon.
Figure 1. Technician port
Connect an Ethernet cable between the port of the personal computer that is configured in step
2 and
the technician port.
After the connection is made, the system will automatically configure the IP and DNS
settings for the personal computer if DHCP is available. If it is not available, the system uses the
values that you provided in step 2.
After the Ethernet port of the personal computer is connected, open a supported browser and
browse to address https://install.internal. (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.
Note: If the system cannot be initialized, you are directed to the service assistant
interface.
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, DNS, and gateway.
Add any additional nodes in the order to the system you just created for the first enclosure in
the order.
If the customer has multiple nodes in the order, find the "Management address and service
address information worksheet" that the customer filled out.
Determine if you should add the additional nodes to the system that you created for the first
node for which you just completed the service setup. (The customer might prefer to add additional
candidate nodes to existing systems on their own.)
To add a new candidate node to an existing system, log onto the management GUI using the same
user name and password that you used to complete the service setup for the first control enclosure.
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 10 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.internal
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.
