This is an old revision of the document!
Table of Contents
SVC initialization
On SVC the first SVC node you have to set a cluster IP address by using the front panel. It's highly recommended to set also a service IP address on first port, also from front panel. To access it do
https://<service_IP>/service
The next step is to initialize the cluster, you can access it using a web browser on https
superuser password (default = passw0rd), and answer to the questions.
Now you have an half cluster, because a second node is required. Create a SAN zone between all SVC nodes to be able to add them to the cluster.
Create a cluster on command line:
You can connect on service IP with SSH:
satask mkcluster -clusterip 10.10.3.5 -gw 10.10.3.254 -mask 255.255.255.0
Next step is to initialize the SVC cluster with command line:
svctask chcluster -name svc-c1 svctask chcurrentuser -password ******** svctask chlicense -flash 0 svctask chlicense -remote 0 svctask chlicense -virtualization 90 svctask chlicense -compression 0 svctask chsystem -easysetup no
V7000 initialization
Be carefull, V7000 has predefined services IP addresses.
node canister 1: 192.168.70.121/255.255.255.0 gw 192.168.70.1
node canister 1: 192.168.70.122/255.255.255.0 gw 192.168.70.1
The normal situation is to use the USB key provided by IBM and start the inittool to create the file satask.txt which contain the following command:
satask mkcluster -clusterip 10.10.3.5 -gw 10.10.3.254 -mask 255.255.255.0
ATTENTION: Inittool running under Windows x64 writes a wrong file to the USB key.
Once inserted into V7000 an amber fault LED on the node canister flashes (on back). When the amber fault LED stops flashing, remove the USB key, and check the result file on the USB key. If everything is right, you can connect to SVC
https://<cluster_IP>
Reset Superuser password
Put on your usb key in satask.txt file the following line
satask resetpassword
–> default password: passw0rd
Connection without password
You can connect using ssh without password. Generate a pair of ssh keys on your server, and copy the public key to the /tmp of the SVC node.
IBM_2145:svc-c1:superuser> svctask chcurrentuser -keyfile /tmp/id_dsa.pub
Also possible to add a public key using the web interface on user properties.
For information if you deploy a public key with superuser, the other with less rights are also available.
