![]() |
|||
![]() |
![]() ![]() |
![]() |
![]() ![]() |
![]() |
![]() ![]() |
![]() |
| |||||||||||||||||||||||||||||||||||||||||||||||
|
# cp -r build-server-smct-dir installation-server-dir |
Where build-server-smct-dir is the entire SMCT environment on the build server.
If the flash archives are already stored in the smct-dir/flash directory, do not transfer them again.
Copy the flash archive(s) from the build server to a directory on the installation server.
If the flash archives are already located in smct-dir/flash on the build server and have already been copied, you do not need to perform this step.
Complete the cluster configuration files as described in Chapter 5, Configuration Stage 1: Creating a Generic Flash Archive.
On the installation server, run the nhsmctsetup command:
# /opt/SUNWcgha/nhsmct/bin/nhsmctsetup -d -w smct-dir -s solaris-dir |
The nhsmctsetup command installs all the flxxx and slxxx tools on the installation server.
For more information, see the nhsmctsetup(1M) man page.
If one of the following is true, perform the following procedure before running the fldeploy command:
You are using your build server as an installation server
Your prototype machine is also acting as a master-eligible or a dataless node at deployment time
Modify the /etc/ethers and /etc/hosts files on the build server to remove any references to the prototype machine.
If the existing configuration information is not removed from these files, an error is generated by the fldeploy command.
This section describes how to add cluster-specific configuration data to the machine.conf file.
Add the cluster-specific information to the machine.conf file for each node group by using the information in the following table.
Table 7-1 The machine.conf Parameters Configured in Stage 3
Data | Master-Eligible | Dataless | Diskless |
---|---|---|---|
Yes | Yes | Yes | |
Yes | Yes | Yes, only if MAC_ADDR_POLICY is configured for the diskless node boot policy. | |
Yes | Yes | Yes | |
Optional | Optional | Optional | |
No | No | Yes, only if STATIC_CLIENT_ID_POLICY is configured for the diskless node boot policy. |
In the machine.conf file, configure the Ethernet address of the NIC connected to the installation server.
In the network.conf file, check that the IP address assigned to this NIC is on the same subnet as the installation server.
This section describes how to add cluster-specific network data to the network.conf file.
Add the cluster-specific data to the network.conf file for each node group by using the information in the following table.
Table 7-2 The network.conf Parameters Configured in Stage 3
Data | Master-eligible | Dataless | Diskless |
---|---|---|---|
Yes | Yes | Yes | |
Optional | Optional | Optional | |
Network address and netmask information for physical network interfaces and virtual network interfaces | Yes | Yes | No |
The IP addressing is referred to in the cluster.conf and machine.conf files with the following keywords:
domain keyword in the cluster.conf file
nic and switch keywords in the machine.conf file
The following procedure describes how to configure CMM and CGTP in the network.conf file. This must match the CMM and CGTP configuration in the machine.conf file.
Define the three subnetworks required by CGTP.
These are two physical networks and one CGTP network, using the network configuration element in the network.conf file, for example:
ELEMENT network phys-A type IPV4 number 10.101.1.0 netmask 255.255.255.0 ELEMENT network phys-B type IPV4 number 10.101.2.0 netmask 255.255.255.0 ELEMENT network cgtp type IPV4 number 10.101.3.0 netmask 255.255.255.0 |
Assign the following roles to the NIC connections on each node:
CGTP, CGTP_NIC0, and CGTP_NIC1 in the machine.conf file, for example:
ELEMENT nic nic0@peerNode1 device hme0 address 8:0:20:da:8a:16 type PHYSICAL class PRIMARY role CGTP_NIC0 USE ip peerNode1-2N-nic0 ELEMENT nic nic1@peerNode1 device hme1 type PHYSICAL class SECONDARY role CGTP_NIC1 USE ip peerNode1-2N-nic1 ELEMENT nic cgtp@peerNode1 device cgtp0 type VIRTUAL class SECONDARY role CGTP USE ip peerNode1-2N-cgtp |
Configure an address triplet for each node in the network.conf file.
This is one address per interface. Each address is based on the appropriate subnet, depending on the role of the interface. For example:
ELEMENT ip peerNode1-2N-nic0 address 10.101.1.10 type STATIC alias node1 BELONG_TO network phys-A ELEMENT ip peerNode1-2N-nic1 address 10.101.2.10 type STATIC BELONG_TO network phys-B ELEMENT ip peerNode1-2N-cgtp alias peerNode1-2N-cgtp.localdomain address 10.101.3.10 type STATIC BELONG_TO network cgtp |
Configure the cluster domain.
Add the domainid, the floating address triplet, abd tge CGTP network to the cluster.conf and network.conf files.
For example, in the cluster.conf file, specify the following:
ELEMENT domain cluster_domain id 101 INVOLVE network phys-A network phys-B network cgtp USE ip master-cgtp ip master-nic0 ip master-nic1 |
For example, in the network.conf file, specify the following:
ELEMENT ip master-cgtp address 10.101.3.1 type FLOATING alias master BELONG_TO network cgtp ELEMENT ip master-nic0 address 10.101.1.1 type FLOATING BELONG_TO network phys-A ELEMENT ip master-nic1 address 10.101.2.1 type FLOATING BELONG_TO network phys-B |
![]() ![]() |