Cluster Server 7.4.1 Administrator's Guide - Linux
- 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
- 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 issues with systemd unit service files
- 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
Adding and removing LLT links
You can use the lltconfig command to add or remove LLT links when LLT is running.
See the lltconfig(1M) manual page for more details.
Note:
When you add or remove LLT links, you need not shut down GAB or the high availability daemon, had. Your changes take effect immediately, but are lost on the next restart. For changes to persist, you must also update the /etc/llttab
file.
To add LLT links
- Where:
Depending on the LLT link type, run the following command to add an LLT link:
For ether link type:
# lltconfig -t devtag -d device [-b ether ] [-s SAP] [-m mtu] [-I] [-Q]
For UDP link type:
# lltconfig -t devtag -d device -b udp [-s port] [-m mtu] -I IPaddr -B bcast
For UDP6 link type:
# lltconfig -t devtag -d device -b udp6 [-s port] [-m mtu] -I IPaddr [-B mcast]
For RDMA link type:
# lltconfig -t devtag -d device -b rdma -s port [-m mtu] -I IPaddr -B bcast
devtag
Tag to identify the link
device
Device name of the interface.
For link type ether, you can specify the device name as an interface name. For example, eth0. Preferably, specify the device name as eth-macaddress. For example, eth- xx:xx:xx:xx:xx:xx.
For link types udp and udp6, the device is the udp and udp6 device name respectively.
For link type rdma, the device name is udp.
bcast
Broadcast address for the link type udp and rdma
mcast
Multicast address for the link type udp6
IPaddr
IP address for link types udp, udp6 and rdma
SAP
SAP to bind on the network links for link type ether
port
Port for link types udp, udp6 and rdma
mtu
Maximum transmission unit to send packets on network links
For example:
For ether link type:
# lltconfig -t eth4 -d eth4 -s 0xcafe -m 1500
For UDP link type:
# lltconfig -t link1 -d udp -b udp -s 50010 -I 192.168.1.1 -B 192.168.1.255
For UDP6 link type:
# lltconfig -t link1 -d udp6 -b udp6 -s 50010 -I 2000::1
For RDMA link:
# lltconfig -t link1 -d udp -b rdma -s 50010 -I 192.168.1.1 -B 192.168.1.255
Note:
If you want the addition of LLT links to be persistent after reboot, then you must edit the
/etc/lltab
with LLT entries.
To remove an LLT link
- Run the following command to disable a network link that is configured under LLT.
# lltconfig -t devtag -L disable
- Wait for the 16 seconds (LLT peerinact time).
- Run the following command to remove the link.
# lltconfig -u devtag