![]() |
|||
![]() |
![]() ![]() |
![]() |
![]() ![]() |
![]() |
![]() ![]() |
![]() |
| |||||||||||||||||||||||||||||||||||||||||||||||
|
# patchadd -M /NetraHASuite/Patches/ patch-name |
After the Solaris operating system has been installed on the dataless node, install the Foundation Services on the dataless node.
The set of services to be installed on the dataless node is a subset of the Foundation Services installed on the master-eligible nodes. Install the packages that are listed in the following table.
Table 8-2 Foundation Services Packages for Dataless Nodes
Package Name | Package Description |
---|---|
SUNWnhadm | Cluster administration tool |
SUNWnhhb | Probe heartbeat module |
SUNWnhcmd | CMM developer package (.h and .so files) |
SUNWnhcma | CMM binaries |
SUNWnhcmb | CMM binaries |
SUNWnhcdt | Trace library |
SUNWnhtp8 or SUNWnhtp9 | CGTP kernel drivers and modules |
SUNWnhtu8 or SUNWnhtu9 | CGTP user-space components, configuration scripts, and files |
SUNWjsnmp | Java DMK 5.0 SNMP manager API classes |
SUNWnhmas | NMA configuration and startup script |
SUNWnhpma | Daemon monitor /opt file system |
SUNWnhpmb | Daemon monitor root file system |
SUNWnhpms | Daemon monitor scripts |
SUNWnhpmn | Daemon monitor scripts |
SUNWnhpmm | Daemon monitor driver |
SUNWlomr | LOM package required if you install the Watchdog Timer |
SUNWlomu | LOM package required if you install the Watchdog Timer |
SUNWnhwdt | Watchdog Timer required only if the dataless node is not a CompactPCI board |
Mount the installation server directory on the dataless node as described in To Mount an Installation Server Directory on the Master-Eligible Nodes.
Install the packages by using the pkgadd command:
# pkgadd -d /NetraHASuite/Packages/ package-name |
where /NetraHASuite/Packages is the installation server directory that is mounted on the dataless node.
CGTP enables a redundant network for your cluster.
Note - If you do not require CGTP, do not install the CGTP packages. For more information about the impact of not installing CGTP, see Choosing a Cluster Network.
The following procedures explain how to configure the Foundation Services on a dataless node.
# touch /etc/notrouter |
Because the cluster network is not routable, the dataless nodes must be disabled as routers.
Modify the /etc/default/login file so you can connect to the node from a remote system as superuser:
# mv /etc/default/login /etc/default/login.orig # chmod 644 /etc/default/login.orig # sed '1,$s/^CONSOLE/#CONSOLE/' /etc/default/login.orig > /etc/default/login # chmod 444 /etc/default/login |
Disable power management:
# touch /noautoshutdown |
Modify the .rhosts file according to the security policy for your cluster:
# cp /.rhosts /.rhosts.orig # echo "+ root" > /.rhosts # chmod 444 /.rhosts |
# /usr/sbin/eeprom local-mac-address?=true # /usr/sbin/eeprom auto-boot?=true # /usr/sbin/eeprom diag-switch?=false |
(Optional) If using the Network Time Protocol (NTP) to run an external clock, configure the dataless node as an NTP server.
This procedure is described in the Solaris documentation.
To configure external IP addresses for a dataless node, the node must have an extra physical network interface or logical network interface. A physical network interface is an unused interface on an existing Ethernet card or a supplemental HME or QFE Ethernet card, for example, hme2. A logical network interface is an interface configured on an existing Ethernet card, for example, hme1:101.
Configure an external IP address for the extra network interface based on your public network policy.
Log in to the dataless node as superuser.
As for the master-eligible nodes, three IP addresses are configured for each dataless node:
The IP address for the first network interface, NIC0
The IP address for the second network interface, NIC1
The IP address for the virtual network interface, cgtp0
The IP addresses can be IPv4 addresses of any class. However, the nodeid that you later define in the cluster_nodes_table file and the nhfs.conf file must be a decimal representation of the host part of the node's IP address. For information about the files, see To Create the nhfs.conf File for a Dataless Node and To Update the Cluster Node Table.
Create or update the file /etc/hostname.NIC0 for the NIC0 interface.
This file must contain the cluster network name of the dataless node on the second interface, for example, netraDATALESS1-nic0.
Create or update the file /etc/hostname.NIC1 for the NIC1 interface.
This file must contain the cluster network name of the master-eligible node on the second interface, for example, netraDATALESS1-nic1.
Create or update the file /etc/hostname.cgtp0 for the cgtp0 interface.
This file must contain the cluster network name of the dataless node on the cgtp0 interface, for example, netraDATALESS1-cgtp.
In the /etc/hosts file, add the IP address and node name for the NIC0, NIC01, and cgtp0 network interfaces of all the nodes in the cluster.
127.0.0.1 localhost 10.250.1.10 netraMEN1 10.250.2.10 netraMEN1-nic1 10.250.3.10 netraMEN1-cgtp 10.250.1.20 netraMEN2 10.250.2.20 netraMEN2-nic1 10.250.3.20 netraMEN2-cgtp 10.250.1.30 netraDATALESS1-nic0 loghost netraDATALESS1.localdomain 10.250.2.30 netraDATALESS1-nic1 netraDATALESS1-nic1.localdomain 10.250.3.30 netraDATALESS1-cgtp netraDATALESS1-cgtp.localdomain 10.250.1.1 master 10.250.2.1 master-nic1 10.250.3.1 master-cgtp |
Update the /etc/nodename file with the name corresponding to the address of one of the network interfaces, for example, netraDATALESS1-cgtp.
Create the /etc/netmasks file by adding one line for each subnet on the cluster:
10.250.1.0 255.255.255.0 10.250.2.0 255.255.255.0 10.250.3.0 255.255.255.0 |
![]() ![]() |