Patch-ID# 115644-05 Keywords: netra, high, availability, suite, saratoga Synopsis: NHAS 2.1 foundation services: Installer patch Date: Mar/07/2005 Install Requirements: NA Solaris Release: 8 9 SunOS Release: 5.8 5.9 Unbundled Product: Netra High Availability Suite Unbundled Release: 2.1_6/03 Xref: Topic: Relevant Architectures: sparc BugId's fixed with this patch: 4651306 4846389 4846399 4851740 4858445 4860151 4866767 4869517 4870436 4887863 4889120 4904926 4918892 4926683 4926708 4926731 4930283 4937927 4938737 4942394 4942413 4964402 4974735 4976748 4978748 4984580 5007052 5033687 5100157 6179864 6180361 6181876 6181880 Changes incorporated in this version: 4869517 4942394 5100157 6179864 6180361 6181876 6181880 Patches accumulated and obsoleted by this patch: Patches which conflict with this patch: Patches required with this patch: Obsoleted by: Files included with this patch: /opt/SUNWcgha/config.standard/addon.conf.NETRA-120.template /opt/SUNWcgha/config.standard/addon.conf.NETRA-20.template /opt/SUNWcgha/config.standard/addon.conf.NETRA-CT.template /opt/SUNWcgha/config.standard/addon.conf.NETRA-T1.template /opt/SUNWcgha/config.standard/addon.conf.template /opt/SUNWcgha/config.standard/cluster_definition.conf.template /opt/SUNWcgha/config.standard/env_installation.conf.template /opt/SUNWcgha/config.standard/nodeprof.conf.template /opt/SUNWcgha/lib/ins/conf/os/common_product.conf /opt/SUNWcgha/lib/ins/conf/os/node_s28s_hw3wos_05a.conf /opt/SUNWcgha/lib/ins/conf/os/node_s8u7_108528-21.conf /opt/SUNWcgha/lib/ins/conf/os/node_s9_update_gt_5.conf /opt/SUNWcgha/lib/ins/conf/os/product_s28s_hw1wos_06a.conf /opt/SUNWcgha/lib/ins/conf/os/product_s28s_hw3wos_05a.conf /opt/SUNWcgha/lib/ins/conf/os/product_s28s_u7wos_08a.conf /opt/SUNWcgha/lib/ins/conf/os/product_s8u7_108528-21.conf /opt/SUNWcgha/lib/ins/conf/os/product_s9_58shwpl3.conf /opt/SUNWcgha/lib/ins/conf/os/product_s9_update_gt_5.conf /opt/SUNWcgha/lib/ins/conf/os/product_s9s_u1wos_08b.conf /opt/SUNWcgha/lib/ins/conf/os_description.conf /opt/SUNWcgha/lib/ins/tools/install_os/common/checker.pl /opt/SUNWcgha/lib/ins/tools/install_os/common/dataless_cmm.pl /opt/SUNWcgha/lib/ins/tools/install_os/common/dataless_fsconf.pl /opt/SUNWcgha/lib/ins/tools/install_os/common/diskless_cgtp.pl /opt/SUNWcgha/lib/ins/tools/install_os/common/diskless_cmm.pl /opt/SUNWcgha/lib/ins/tools/install_os/common/diskless_end.pl /opt/SUNWcgha/lib/ins/tools/install_os/common/diskless_fsconf.pl /opt/SUNWcgha/lib/ins/tools/install_os/common/diskless_rbs.pl /opt/SUNWcgha/lib/ins/tools/install_os/common/diskless_sm.pl /opt/SUNWcgha/lib/ins/tools/install_os/common/diskless_solaris.pl /opt/SUNWcgha/lib/ins/tools/install_os/common/ins_soldistrib.pl /opt/SUNWcgha/lib/ins/tools/install_os/common/install_server.pl /opt/SUNWcgha/lib/ins/tools/install_os/common/jdk.pl /opt/SUNWcgha/lib/ins/tools/install_os/common/local_cgtp.pl /opt/SUNWcgha/lib/ins/tools/install_os/common/local_check.pl /opt/SUNWcgha/lib/ins/tools/install_os/common/local_end.pl /opt/SUNWcgha/lib/ins/tools/install_os/common/ma_jdmk.pl /opt/SUNWcgha/lib/ins/tools/install_os/common/men_cmm.pl /opt/SUNWcgha/lib/ins/tools/install_os/common/men_fsconf.pl /opt/SUNWcgha/lib/ins/tools/install_os/common/men_rnfs.pl /opt/SUNWcgha/lib/ins/tools/install_os/common/men_svm.pl /opt/SUNWcgha/lib/ins/tools/install_os/common/pmd.pl /opt/SUNWcgha/lib/ins/tools/install_os/common/sol_jumpstart.pl /opt/SUNWcgha/lib/ins/tools/install_os/common/soladd.pl /opt/SUNWcgha/lib/ins/tools/install_os/common/wdt.pl /opt/SUNWcgha/lib/ins/tools/lib/addon.pl /opt/SUNWcgha/lib/ins/tools/lib/common.pl /opt/SUNWcgha/lib/ins/tools/lib/component.pl /opt/SUNWcgha/lib/ins/tools/lib/conf.pl /opt/SUNWcgha/lib/ins/tools/lib/dialog.pl /opt/SUNWcgha/lib/ins/tools/lib/mount_for_diskless.pl /opt/SUNWcgha/lib/ins/tools/lib/nhinstall.pl /opt/SUNWcgha/lib/ins/tools/lib/parser.pl /opt/SUNWcgha/lib/ins/tools/lib/product.pl /opt/SUNWcgha/lib/ins/tools/lib/reboot.pl /opt/SUNWcgha/lib/ins/tools/lib/sequencer.pl /opt/SUNWcgha/lib/ins/tools/lib/variables.pm /opt/SUNWcgha/lib/ins/tools/lib/wait_boot.pl /opt/SUNWcgha/lib/ins/tools/lib/wait_sndr.pl /opt/SUNWcgha/nhsmct/etc/jumpstart/release /opt/SUNWcgha/nhsmct/etc/services/SNDR.SPARC.SOLARIS /opt/SUNWcgha/nhsmct/etc/services/Solaris_8psr1/PATCH_DATALESS.SPARC.SOLARIS /opt/SUNWcgha/nhsmct/etc/services/Solaris_8psr1/PATCH_DISKLESS.SPARC.SOLARIS /opt/SUNWcgha/nhsmct/etc/services/Solaris_8psr1/PATCH_MASTER_ELIGIBLE.SPARC.SOLARIS /opt/SUNWcgha/nhsmct/etc/services/Solaris_8psr3/CGTP.SPARC.SOLARIS /opt/SUNWcgha/nhsmct/etc/services/Solaris_8psr3/PATCH_DATALESS.SPARC.SOLARIS /opt/SUNWcgha/nhsmct/etc/services/Solaris_8psr3/PATCH_DISKLESS.SPARC.SOLARIS /opt/SUNWcgha/nhsmct/etc/services/Solaris_8psr3/PATCH_MASTER_ELIGIBLE.SPARC.SOLARIS /opt/SUNWcgha/nhsmct/etc/services/Solaris_8psr3/RNFS.SPARC.SOLARIS /opt/SUNWcgha/nhsmct/lib/sl_jumpstart.pl /opt/SUNWcgha/sbin/nhinstall /opt/SUNWcgha/nhsmct/etc/jumpstart/Solaris_8psr3/profile.proto Problem Description: 6181876 nhinstall gives an incorrect path of "1" when adding AVS package SUNWscmu 6180361 Reboot of dataless is not required when adding a node 6179864 Adding a new node doesn't update /etc/hosts on a existing dataless 6181880 NHAS should be supported on Solaris 9 4/04 (aka S9U6) 5100157 Dataless installation support 4869517 Network Interface Names Are Found To Be Invalid During DHCP Startup 4942394 nhinstall says "You can now boot your diskless nodes" when there are none (from 115644-04) This patch revision was uprev'ed to keep its revision aligned with 115606-04. (from 115644-03) 5033687 default_route param is empty in sysidcfg files if no public network is defined 4651306 Diskless Node Does Not Boot After Failover 4846389 [RFE] Sequential synchronising of partitions 4860151 Diskless ct410 client boot hangs trying to access master-cgtp node 4937927 nhinstall does not detect empty SOLARIS_DIR 4938737 nhintall should be able to manage the package and patch installation order 4942413 nhinstall must not prevent installation if /export is too small 4976748 NHAS must support full Sanibel chassis (18 nodes), with RR HW and SW (DVD11) 4978748 Request for support of 2xN240 + 36 CP2300 configuration, for customer. 5007052 cannot specify a router different from the installation server 4984580 The DATA_MGT_POLICY directive is incorrectly processed and described (from 115644-02) 4846399 [RFE] Tunable to delay start of synchronisation 4918892 The "lack of membership" timeout that reboots MINs should be configurable 4974735 The RNFS.CheckReplicatedSlices property must be 'false' by default 4964402 New SNDR patch 116710-01: nhinstall and checker must be adapted (from 115644-01) 4930283 nhinstall:fake error when checking Partitions replication during install SVM/NHA 4858445 nhinstall patching for diskless nodes is not clear 4866767 Installing a 2-Node Cluster With nhinstall Fails If NMEN_INTERFACES Not Defined 4926683 nhinstall must not prevent a cluster with more than 12 nodes to be installed 4926708 Failure during umount when installing the patch 109134-28 4926731 dmfe driver requires MEN to be rebooted twice after solaris installation 4889120 Adaptability Data Management Policy is not supported 4887863 DATA_MGT_POLICY does not respect installer directive policy: values in uppercase 4851740 CGTP Patch T112281-02 Does Not Support Solaris 8 PSR 1 4904926 CGTP patch does not support Solaris 8 PSR 3 4870436 The addon.conf.NETRA-120.template File Is Not Contained In the Delivery Patch Installation Instructions: -------------------------------- Refer to the man pages for instructions on using 'patchadd' and 'patchrm' scripts provided with Solaris. Any other special or non-generic installation instructions are described below as special instructions. The following example installs a patch to a stand-alone machine: example# patchadd /var/spool/patch/104945-02 The following example removes a patch from a stand-alone system: example# patchrm 104945-02 For additional examples please see the appropriate man pages. ---------------------------------------------------------------------- FEATURE DETAILS ---------------------------------------------------------------------- For information on changes provided in patches of version -03 or earlier, see the product documentation update available in patch 114170. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 5100157 Dataless installation support ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ To install dataless nodes with nhinstall, new parameters have been added to the following files: env_installation.conf --------------------- A new option, DISKLESS_DATALESS_INSTALL, has been added to the SOLARIS_INSTALL parameter. If you choose the DISKLESS_DATALESS_INSTALL option, the Solaris operating system should already be installed on the nodes before running the nhinstall tool. When you launch the nhinstall tool, the Solaris services for the diskless and dataless nodes are installed. A new parameter, DATALESS_SOLARIS_DIR, has been added to env_installation.conf. This parameter identifies the location of the Solaris distribution for dataless nodes, if this distribution is not the same as that installed on the other nodes in the cluster. By default, the Solaris distribution installed on the master-eligible nodes is used for DATALESS_SOLARIS_DIR. DATALESS_SOLARIS_DIR=$SOLARIS_DIR addon.conf ---------- A new parameter, DATALESS, has been added to addon.conf. This parameter indicates a patch or package is to be installed for a dataless node. Options are Y or N. This parameter is ignored if the value of the scope parameter is set to SHARED. dataless_nodeprof.conf ---------------------- This is a new file. Creating the dataless_nodeprof.conf file enables you to customize the Solaris installation on dataless nodes. When this file is present in the local directory on the installation server, the file's contents supersede the contents of both the nodeprof.conf file and the default profile file that nhinstall uses for dataless node installation. If the dataless_nodeprof.conf file exists, nhinstall uses the nodeprof.conf file for details of the Solaris profile it is to install on the master-eligible nodes and the dataless_nodeprof.conf file for the Solaris profile it is to install on the dataless nodes. If you want to install the same Solaris profile on master-eligible and dataless nodes, do not create a dataless_nodeprof.conf file. For information about the format and contents of the dataless_nodeprof.conf file, see the nodeprof.conf file and Preparing Custom JumpStart Installations (Tasks) in the Solaris Installation Guide. cluster_definition.conf ----------------------- The NODE parameter is being deprecated and support for this parameter will be removed in a future release. To replace the NODE parameter, you can use the MEN, DISKLESS, and DATALESS parameters. Do not mix the use of the NODE parameter with the MEN, DISKLESS or DATALESS parameters. MEN Define each master-eligible node. If you do not define the NODE keyword, it is mandatory to define this keyword. If you do define the NODE keyword, do not define this parameter. When you define the MEN keyword, create an entry for each master-eligble node using the following format: MEN=nodeid MAC0 - {name|-} {NIC0|-} {NIC1|-} public-name public-IP public-NIC nodeid The ID of the node used to define IP addresses for the node. This option is mandatory. MAC0 The Ethernet address of the first network interface of the node. This option is mandatory. This address is required to boot the master-eligible node from the installation server. - The Ethernet address of the second network interface of the node is ignored and you must specify a hyphen (-). name Name of the node. By default, the names are assigned as follows: MEN-Cclusterid-Nnodeid NIC0 Name of the first network interface. By default the first value defined for the MEN_INTERFACES parameter is used for NICO. To use the default value, you must specify a hyphen (-). NIC1 Name of the second network interface. By default the first value defined for the MEN_INTERFACES parameter is used for NIC1. To use the default value, you must specify a hyphen (-). public-name Name of the node on the public network different from the name defined with the name parameter. If PUBLIC_NETWORK is not defined, the public-name is ignored. public-ip IP address of the node on the public network. If PUBLIC_NETWORK is not defined, the public-ip is ignored. public-nic Network interface for the node supporting the public network. This can be either a physical network interface or an alias. If PUBLIC_NETWORK is not defined, the public-nic is ignored. Example 1: MEN=10 08:00:20:f9:c5:54 - node10 MEN=20 08:00:20:f9:a8:12 - node20 Example 2: MEN=10 08:00:20:f9:c5:54 - node10 - - FSNode1 192.168.12.5 hme1:5 MEN=20 08:00:20:f9:a8:12 - node20 - - FSNode2 192.168.12.6 hme1:101 There are two entries, one for each of the master-eligible nodes. The nhinstall tool first installs the product on the first master-eligible node defined and then on the second master-eligible node. DISKLESS Define each diskless node. To define a node you must either define the DISKLESS parameter for this node or add the definition of this node to the NODE parameter. There is an entry for each diskless node and each entry has the following format: DISKLESS=nodeid {MAC0|client-id|-} {MAC1|-} {name|-} {NIC0|-} {NIC1|-} public-name public-IP public-NIC nodeid The ID of the node used to define IP addresses for the node. This option is mandatory. MAC0 | client-id | - The Ethernet address of the first network interface of the node. This option is mandatory. Whether this value is required depends on the DHCP boot policy used: For the DHCP static boot policy, when the DISKLESS_BOOT_POLICY is set to DHCP_STATIC, specify the Ethernet address of the first network interface of the node. For the DHCP dynamic boot policy, when the DISKLESS_BOOT_POLICY is set to DHCP_DYNAMIC, the MAC0 address is ignored and you must specify a hyphen (-). For the DHCP client ID boot policy, when the DISKLESS_BOOT_POLICY is set to DHCP_CLIENT_ID, specify the client ID as a string in double quotation marks. You can insert a hexadecimal value, for example /00999:88:05. NOTE: If you want to include the back slash character, you must include it twice. MAC1 The Ethernet address of the second network interface of the node. This option is mandatory. This value is required depending on the DHCP boot policy used: For the DHCP static boot policy, when the DISKLESS_BOOT_POLICY is set to DHCP_STATIC, specify the Ethernet address of the second network interface of the node. For the DHCP dynamic boot policy, when the DISKLESS_BOOT_POLICY is set to DHCP_DYNAMIC, the MAC1 address is ignored and you must specify a hyphen (-). For the DHCP client ID boot policy, when the DISKLESS_BOOT_POLICY is set to DHCP_CLIENT_ID, the MAC1 address is ignored and you must specify a hyphen (-). name Name of the node. By default, the names are assigned as follows: NMEN-Cclusterid-Nnodeid Do not use underscores (_) when naming a node. For more information, see hosts(4). NIC0 Name of the first network interface. If you want to use the default value, which is the first value defined by the NMEN_INTERFACES parameter, specify a hyphen (-). NIC1 Name of the second network interface. If you want to use the default value, which is the second value defined by the NMEN_INTERFACES parameter, specify a hyphen (-). public-name Name of the node on the public network different from the name defined with the name parameter. If PUBLIC_NETWORK is not defined, the public-name is ignored. public-ip IP address of the node on the public network. If PUBLIC_NETWORK is not defined, the public-ip is ignored. public-nic Network interface for the node supporting the public network. This can be either a physical network interface or an alias. If PUBLIC_NETWORK is not defined, the public-nic is ignored. Example 1: MEN=10 08:00:20:f9:c5:54 - node10 MEN=20 08:00:20:f9:a8:12 - node20 DISKLESS=30 - - node30 DISKLESS=40 - - node40 Example 2: MEN=10 08:00:20:f9:c5:54 - node10 - - FSNode1 192.168.12.5 hme1:5 MEN=20 08:00:20:f9:a8:12 - node20 - - FSNode2 192.168.12.6 hme1:101 DISKLESS=30 - - node30 DISKLESS=40 - - node40 In these examples there are four entries, one entry for each of the master-eligible nodes and two entry for two diskless nodes. The nhinstall tool first installs the product on the first master-eligible node defined, then on the second master-eligible node, and then on the two diskless nodes. To add diskless nodes to a cluster that is already running, add the definitions for the new nodes by using the DISKLESS parameter and run the nhinstall command with the add option. For information about the add option of the nhinstall command, see the nhinstall(1M) man page. DATALESS Define each dataless node. To use this new parameter, you must use the MEN parameter instead of the deprecated NODE parameter. There is an entry for each dataless node and each entry has the following format: DATALESS=nodeid MAC0 - {name|-} {NIC0|-} {NIC1|-} public-name public-IP public-NIC nodeid The ID of the node used to define IP addresses for the node. This option is mandatory. MAC0 The Ethernet address of the first network interface of the node. This option is mandatory. This address is required to boot the dataless node from the installation server. - The Ethernet address of the second network interface of the node. This option is mandatory. The MAC1 address is ignored and you must specify a hyphen (-). name Name of the node. By default, the names are assigned as follows: NMEN-Cclusterid-Nnodeid Do not use underscores (_) when naming a node. For more information, see hosts(4). NIC0 Name of the first network interface. If you want to use the default value, which is the first value defined by the NMEN_INTERFACES parameter, specify a hyphen (-). NIC1 Name of the second network interface. If you want to use the default value, which is the second value defined by the NMEN_INTERFACES parameter, specify a hyphen (-). public-name Name of the node on the public network different from the name defined with the name parameter. If PUBLIC_NETWORK is not defined, the public-name is ignored. public-ip IP address of the node on the public network. If PUBLIC_NETWORK is not defined, the public-ip is ignored. public-nic Network interface for the node supporting the public network. This can be either a physical network interface or an alias. If PUBLIC_NETWORK is not defined, the public-nic is ignored. Example 1: MEN=10 08:00:20:f9:c5:54 - node10 MEN=20 08:00:20:f9:a8:12 - node20 DATALESS=30 08:00:20:f9:c3:ae - node30 DATALESS=40 08:00:20:d2:d5:f7 - node40 Example 2: MEN=10 08:00:20:f9:c5:54 - node10 - - FSNode1 192.168.12.5 hme1:5 MEN=20 08:00:20:f9:a8:12 - node20 - - FSNode2 192.168.12.6 hme1:101 DATALESS=30 08:00:20:f9:c3:ae - node30 DATALESS=40 08:00:20:d2:d5:f7 - node40 In these examples there are four entries, one entry for each of the master-eligible nodes and two entry for two dataless nodes. The nhinstall tool first installs the product on the first master-eligible node defined, then on the second master-eligible node, and then on the two dataless nodes. To add dataless nodes to a cluster that is already running, add the definitions for the new nodes by using the DATALESS parameter and run the nhinstall command with the add option. For information about the add option of the nhinstall command, see the nhinstall(1M) man page. SLICE ----- A new option, scope, has been added to the SLICE parameter. The scope of the definition of the slice. The scope is a comma separated list including values for MEN, DATALESS, and nodeid where the values listed define the nodes to which the slice definition applies. By specifying a type of node such as MEN or DATALESS you apply the slice definition to that type of node. By specifying the nodeid of nodes you can apply the slice definition to a particular set of nodes. DATALESS_OS_REFERENCE --------------------- This new parameter has the same usage as MEN_OS_REFERENCE and DISKLESS_OS_REFERENCE. NMEN_INTERFACES --------------- This parameter is now applicable to both diskless and dataless nodes. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 6181880 NHAS should be supported on Solaris 9 4/04 (aka S9U6) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The nhinstall tool now supports the installation of the following additional Solaris operating system versions: Solaris 9 4/04 s9s_u6wos_08aSPARC Solaris 9 9/04 s9s_u7wos_09 SPARC Special Install Instructions: ---------------------------------------------- None. README -- Last modified date: Monday, March 7, 2005