- Sun Cluster 3.0 Series: Guide to Installation—Part 2
- Objectives
- Prerequisites
- Major Resources
- Introduction
- Sun Cluster 3.0 Software
- Install SC 3.0 On First Cluster Node—Without Reboot
- Identify the Device ID (DID) on the First Cluster Node
- Verify DID is Available on Each Additional Cluster Node)
- Install SC 3.0 Patches on the First Cluster Node
- Verify the Install Mode is Enabled
- Install SC 3.0 on Additional Cluster Nodes— Without Reboot
- Install SC 3.0 Patches on Additional Cluster Nodes
- Establish the SC 3.0 Quorum Device - First Cluster Node Only
- Configure Additional Public Network Adapters - NAFO
- Configure ntp.conf on Each Cluster Node
- Verify /etc/nsswitch Entries
- Update Private Interconnect Addresses on All Cluster Nodes
- Add Diagnostic Toolkit
Like this article? We recommend
Like this article? We recommend
Like this article? We recommend
Section 2.9: Configure Additional Public Network Adapters - NAFO
Each cluster node should be connected to more than one subnet by configuring additional public network adapters for the secondary subnets.
In this section, configure NAFO software for each public network adapter, on each cluster node. This is done in preparation for creating the Resource Group.
NOTE
Refer to Figure 1, and Table 1 through Table 5 of Module 1, (Sun™ Cluster 3.0 Series: Guide to Installation—Part I, Sun BluePrints OnLine, April, 2003) for networking and cabling connections implemented in this configuration exercise.
NAFO configuration guidelines:
Always maintain at least one public network adapter connection for each node in the cluster (SunPlex platform). A cluster node is inaccessible without this connection.
Configure all public network adapters to belong to a NAFO group.
Avoid unconfiguring (unplumbing) or bringing down the active adapter of a NAFO group without first switching over the active adapter to a backup adapter in the group.
For any given node, there can be at most one NAFO group on a given subnet.
All adapters in a given NAFO group must be connected to the same subnet.
Only one adapter in a given NAFO group can have a host name associate, that is, an /etc/hostname.adapter file.
A public network adapter can belong to only one NAFO group.
NOTE
Configure only public network adapters. Do not configure private network adapters.
Step 2.9.1
On each cluster node, use vi to create the /etc/hostname.hme0 file, as indicated in the following codebox. After creating the file entry, verify clustnode1 is configured correctly:
root@clustnode1# more /etc/hostname.hme0 clustnode1
Step 2.9.2
After creating the file entry, verify clustnode2 is configured correctly by entering the following:
root@clustnode2# more /etc/hostname.hme0 clustnode2
NOTE
If a naming service is configured, this information should be in the naming service database.
Step 2.9.3
On each cluster node, configure a NAFO group using the available adapters, by entering the following on clustnode1:
# pnmstat -l
{{verify no existing nafo0 group exists, before proceeding}}
# pnmset -c nafo0 -o create hme0 qfe1
# pnmstat -l
group adapters status fo_time act_adp
nafo0 hme0:qfe1 OK NEVER hme0
NOTE
For local (manual) installations, verify additional failover capabilities on each cluster node. For example, verify that a public network failover occurs successfully between hme0 and qfe1. That is, physically disconnect the public network hme0 cable connection, and manually verify each node is still "accessible" over the same public subnet, qfe1.