InfoScale™ 9.0 Cluster Server Administrator's Guide - Windows
- 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
- Agent classifications
- About cluster control, communications, and membership
- About security services
- About cluster topologies
- VCS configuration concepts
- Introducing Cluster Server
- Section II. Administration - Putting VCS to work
- About the VCS user privilege model
- Getting started with VCS
- Administering the cluster from the command line
- About administering VCS from the command line
- Stopping the VCS engine and related processes
- 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
- About administering resource types
- About administering clusters
- Configuring resources and applications in VCS
- About configuring resources and applications
- About Virtual Business Services
- About Intelligent Resource Monitoring (IMF)
- About fast failover
- How VCS monitors storage components
- About storage configuration
- About configuring network resources
- About configuring file shares
- About configuring IIS sites
- About configuring services
- Before you configure a service using the GenericService agent
- About configuring processes
- About configuring Microsoft Message Queuing (MSMQ)
- About configuring the infrastructure and support agents
- About configuring applications using the Application Configuration Wizard
- Adding resources to a service group
- About application monitoring on single-node clusters
- Configuring the service group in a non-shared storage environment
- About the VCS Application Manager utility
- About testing resource failover using virtual fire drills
- Modifying the cluster configuration
- Section III. Administration - Beyond the basics
- Controlling VCS behavior
- VCS behavior on resource faults
- About controlling VCS behavior at the service group level
- Customized behavior diagrams
- VCS behavior for resources that support the intentional offline functionality
- About controlling VCS behavior at the resource level
- Service group workload management
- Sample configurations depicting workload management
- The role of service group dependencies
- VCS event notification
- VCS event triggers
- List of event triggers
- Controlling VCS behavior
- Section IV. 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 replication resources in VCS
- 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 Cluster Manager (Java console)
- 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
- Connecting clusters–Creating global clusters
- Section V. Troubleshooting and performance
- VCS performance considerations
- How cluster components affect performance
- How cluster operations affect performance
- VCS performance consideration when a system panics
- VCS agent statistics
- Troubleshooting and recovery for VCS
- VCS message logging
- Handling network failure
- Troubleshooting VCS startup
- Troubleshooting service groups
- Troubleshooting and recovery for global clusters
- VCS utilities
- VCS performance considerations
- Section VI. Appendixes
- Appendix A. VCS user privileges—administration matrices
- Appendix B. Cluster and system states
- Appendix C. VCS attributes
- Appendix D. Configuring LLT over UDP
- Appendix E. Handling concurrency violation in any-to-any configurations
- Appendix F. Accessibility and VCS
- Appendix G. Executive Order logging
Verifying LLT
Use the lltstat command to verify the links are active for LLT. This command returns information about the LLT links for the node on which it is typed.
In the following example, lltstat -n is typed on System 0 and System 1 in a private network.
System 0
Drive:\>lltstat -n LLT node information: Node State Links * 0 System 0 OPEN 2 1 System 1 OPEN 2
System 1
Drive:\>lltstat -n LLT node information: Node State Links 0 System 0 OPEN 2 *1 System 1 OPEN 2
Note that each node has two links and each node is in the OPEN state. The asterisk (*) denotes the node on which the command is typed.
If the output of lltstat -n does not show each node in the cluster, or does not show two links for each node, type lltstat -nvv | to view additional information about LLT.
In the following example, lltstat -nvv | more is typed on System 0 in a private network. Note that each node should be OPEN, each link should be UP, and each address should be correct.
Drive:\> lltstat -nvv | more Node State Link Status Address * 0 HOUWIN201 OPEN Adapter0 UP 00:03:47:0D:A8:74 Adapter1 UP 00:03:47:0D:A8:75 1 HOUWIN202 OPEN Adapter0 UP 00:03:47:0D:A4:46 Adapter1 UP 00:03:47:0D:A4:47 2 CONNWAIT Adapter0 DOWN Adapter1 DOWN 3 CONNWAIT Adapter0 DOWN Adapter1 DOWN 4 CONNWAIT Adapter0 DOWN Adapter1 DOWN 5 CONNWAIT Adapter0 DOWN Adapter1 DOWN 6 CONNWAIT Adapter0 DOWN Adapter1 DOWN 7 CONNWAIT Adapter0 DOWN Adapter1 DOWN 8 CONNWAIT Adapter0 DOWN Adapter1 DOWN 9 CONNWAIT Adapter0 DOWN Adapter1 DOWN 10 CONNWAIT Adapter0 DOWN Adapter1 DOWN 12 CONNWAIT Adapter0 DOWN Adapter1 DOWN 13 CONNWAIT Adapter0 DOWN Adapter1 DOWN 14 CONNWAIT Adapter0 DOWN Adapter1 DOWN 15 CONNWAIT Adapter0 DOWN Adapter1 DOWN -- More --
To obtain information only about the configured systems in the cluster, use the lltstat -nvv configured command. See the following example:
Drive:\>lltstat -nvv configured Node State Link Status Address * 0 HOUWIN201 OPEN Adapter0 UP 00:03:47:0D:A8:74 Adapter1 UP 00:03:47:0D:A8:75 1 HOUWIN202 OPEN Adapter0 UP 00:03:47:0D:A4:46 Adapter1 UP 00:03:47:0D:A4:47
To obtain information about the ports open for LLT, type lltstat -p on any node. In the following example, lltstat -p is typed on System 0 in a private network.
Drive:\> lltstat -p LLT port information: Port Usage Cookie 0 gab 0x0 opens: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14... connects: 0 1
Note that two nodes (0 and 1) are connected.