Cluster Server 8.0.2 Administrator's Guide - Solaris
- Section I. Clustering concepts and terminology
- Introducing Cluster Server
- About Cluster Server
- About cluster control guidelines
- About the physical components of VCS
- Logical components of VCS
- Types of service groups
- About resource monitoring
- Agent classifications
- About cluster control, communications, and membership
- About security services
- Components for administering VCS
- About cluster topologies
- VCS configuration concepts
- Introducing Cluster Server
- Section II. Administration - Putting VCS to work
- About the VCS user privilege model
- Administering the cluster from the command line
- About administering VCS from the command line
- About installing a VCS license
- Administering LLT
- Starting VCS
- Stopping the VCS engine and related processes
- Logging on to VCS
- About managing VCS configuration files
- About managing VCS users from the command line
- About querying VCS
- About administering service groups
- Modifying service group attributes
- About administering resources
- Enabling and disabling IMF for agents by using script
- Linking and unlinking resources
- About administering resource types
- About administering clusters
- Configuring applications and resources in VCS
- VCS bundled agents for UNIX
- Configuring NFS service groups
- About NFS
- Configuring NFS service groups
- Sample configurations
- About configuring the RemoteGroup agent
- About configuring Samba service groups
- About testing resource failover by using HA fire drills
- Predicting VCS behavior using VCS Simulator
- Section III. VCS communication and operations
- About communications, membership, and data protection in the cluster
- About cluster communications
- About cluster membership
- About membership arbitration
- About membership arbitration components
- About server-based I/O fencing
- About majority-based fencing
- About the CP server service group
- About secure communication between the VCS cluster and CP server
- About data protection
- Examples of VCS operation with I/O fencing
- About cluster membership and data protection without I/O fencing
- Examples of VCS operation without I/O fencing
- Administering I/O fencing
- About the vxfentsthdw utility
- Testing the coordinator disk group using the -c option of vxfentsthdw
- About the vxfenadm utility
- About the vxfenclearpre utility
- About the vxfenswap utility
- About administering the coordination point server
- About configuring a CP server to support IPv6 or dual stack
- About migrating between disk-based and server-based fencing configurations
- Migrating between fencing configurations using response files
- Controlling VCS behavior
- VCS behavior on resource faults
- About controlling VCS behavior at the service group level
- About AdaptiveHA
- Customized behavior diagrams
- About preventing concurrency violation
- VCS behavior for resources that support the intentional offline functionality
- VCS behavior when a service group is restarted
- About controlling VCS behavior at the resource level
- VCS behavior on loss of storage connectivity
- Service group workload management
- Sample configurations depicting workload management
- The role of service group dependencies
- About communications, membership, and data protection in the cluster
- Section IV. Administration - Beyond the basics
- VCS event notification
- VCS event triggers
- Using event triggers
- List of event triggers
- Virtual Business Services
- Section V. Veritas High Availability Configuration wizard
- Introducing the Veritas High Availability Configuration wizard
- Administering application monitoring from the Veritas High Availability view
- Administering application monitoring from the Veritas High Availability view
- Administering application monitoring from the Veritas High Availability view
- Section VI. Cluster configurations for disaster recovery
- Connecting clusters–Creating global clusters
- VCS global clusters: The building blocks
- About global cluster management
- About serialization - The Authority attribute
- Prerequisites for global clusters
- Setting up a global cluster
- Configuring clusters for global cluster setup
- Configuring service groups for global cluster setup
- About IPv6 support with global clusters
- About cluster faults
- About setting up a disaster recovery fire drill
- Test scenario for a multi-tiered environment
- Administering global clusters from the command line
- About global querying in a global cluster setup
- Administering clusters in global cluster setup
- Setting up replicated data clusters
- Setting up campus clusters
- Connecting clusters–Creating global clusters
- Section VII. Troubleshooting and performance
- VCS performance considerations
- How cluster components affect performance
- How cluster operations affect performance
- VCS performance consideration when a system panics
- About scheduling class and priority configuration
- VCS agent statistics
- About VCS tunable parameters
- Troubleshooting and recovery for VCS
- VCS message logging
- Gathering VCS information for support analysis
- Troubleshooting the VCS engine
- Troubleshooting Low Latency Transport (LLT)
- Troubleshooting Group Membership Services/Atomic Broadcast (GAB)
- Troubleshooting VCS startup
- Troubleshooting service groups
- Troubleshooting resources
- Troubleshooting sites
- Troubleshooting I/O fencing
- Fencing startup reports preexisting split-brain
- Troubleshooting CP server
- Troubleshooting server-based fencing on the VCS cluster nodes
- Issues during online migration of coordination points
- Troubleshooting notification
- Troubleshooting and recovery for global clusters
- Troubleshooting licensing
- Licensing error messages
- Troubleshooting secure configurations
- Troubleshooting wizard-based configuration issues
- Troubleshooting issues with the Veritas High Availability view
- VCS message logging
- VCS performance considerations
- Section VIII. Appendixes
Enabling or disabling faster detection of LLT link failure
After installing and configuring VCS, you can enable or disable faster detection of LLT link failure at run time using the lltconfig command.
See the lltconfig (1M) manual page for more information.
To enable faster detection of link failure, LLT requires an additional link which is used to propagate the link-down event to all the cluster nodes that are connected using switches. This type of addition link is called the LLT "hidden" link. The LLT hidden link is not visible to the LLT clients and is not considered in the cluster membership computation. These hidden links are also not meant for any application data communication. Veritas recommends that you configure your public link as "hidden" link instead of configuring it as a low-pri link. Thus, the resource failover may happen as soon as the private links are down. Veritas recommends that you do not use a low priority link as "hidden" link.
Note:
If you have a two-node cluster where the nodes are connected using cross-over cable, then you just need to enable this feature using the lltconfig -j command. You need not configure "hidden" link.
To enable faster detection of link failure on cluster nodes connected using switch
Configure an LLT hidden link:
To configure an existing low-pri link as hidden link, perform the following steps:
Remove the low-pri link on all the nodes.
Add this link as an LLT hidden link using the lltconfig command. Use the -Q option to mark this link as hidden.
For example:
For SPARC:
lltconfig -t hme0 -d /dev/hme:0 -l -Q
For x64:
lltconfig -t bge0 -d /dev/bge:0 -l -Q
Update the
/etc/llttab
configuration file to make this change boot-persistent. You must add the keyword "hidden" at the end of link entry. For example,For SPARC:
link-lowpri hme0 /dev/hme:0 - ether - - hidden
For x64:
link-lowpri bge0 /dev/bge:0 - ether - - hidden
To add a new link as an LLT hidden link, perform the following steps:
Add the new link as an LLT hidden link using the lltconfig command. Use the -Q option to mark this link as hidden. For example,
For SPARC:
lltconfig -t hme0 -d /dev/hme:0 -l -Q
For x64:
lltconfig -t bge0 -d /dev/bge:0 -l -Q
Add this new link to the
/etc/llttab
configuration file to make this change boot-persistent. You must add the keyword "hidden" at the end of link entry. For example,For SPARC:
link-lowpri hme0 /dev/hme:0 - ether - - hidden
For x64:
link-lowpri bge0 /dev/bge:0 - ether - - hidden
- Run the lltstat -l command to view the details of the LLT "hidden" links that you have configured.
The command output must display the "hidden" keyword for the hidden link:
For SPARC:
link 0 hme0 on etherfp lowpri hidden
For x64:
link 0 bge0 on etherfp lowpri hidden
- On each node, run the following command to enable faster detection of link failure:
# lltconfig -j 1
The value 1 is the link failure detection level that enables LLT to detect any link failure immedeiately and process the failure after the LLT "linkstable" timeout period.
- Run the lltstat -c command to verify the value that you configured. For example, the last line in the following sample output shows the link failure detection level that you configured:
# lltstat -c LLT configuration information: node: 0 name: sys1 -- -- retransmit factor: 10 link fail detect level: 1
- Add the following entry to the
/etc/llttab
configuration file to make the change boot-persistent:set-linkfaildetectlevel 1
If you want to change the default value of the linkstable timeout parameter value, perform the following steps:
View the current value of the linkstable parameter:
# lltconfig -T query
To change the value of the parameter:
# lltconfig -T linkstable:value
To make the change boot-persistent, update the
/etc/llttab
configuration file:set-timer linkstable:value
To enable faster detection of link failure on a two-node cluster connected using cross-over cable
- On each node, run the following command:
# lltconfig -j 2
The value 2 is the link failure detection level that enables LLT to detect any link failure immedeiately and process the failure after the LLT "linkstable" timeout period.
- Add the following entry to the
/etc/llttab
configuration file to make the change boot-persistent:set-linkfaildetectlevel 2
To disable faster detection of link failure
- On each node, run the following command to disable faster detection of link failure:
# lltconfig -j 0
The value 0 disables faster link failure detection, and indicates LLT to detect link failures after the LLT "peerinact" time period.
- Remove the following line from the
/etc/llttab
configuration file:set-linkfaildetectlevel value
- If you do not want to enable faster link failure detection, the hidden link remains unused. You can remove the hidden link using the lltconfig command and add it as a low-priority link if necessary.