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. InfoScale event logging
InfoScale log forwarding
Windows Server event logs can be forwarded from a forwarder (source) system to a collector (target) system within the same domain network. You can leverage this Windows Event Forwarding mechanism to forward InfoScale logs from one or more systems to a centralized collector system.
For details on best practices for configuring event log forwarding on Windows Server systems, refer to the Microsoft documentation.
To ensure that WinRM is set up and running on forwarder and collector systems
- Verify the status of the Windows Remote Management (WinRM) service by running the following command (use the Run as Administrator option):
winrm quickconfig
If WinRM is set up and the service is running, the following message is displayed:
WinRM service is already running on this machine. WinRM is already set up for remote management on this computer.
Otherwise, the following message is displayed:
WinRM is not set up to receive requests on this machine. The following changes must be made: Start the WinRM service. Set the WinRM service type to delayed auto start. Make these changes [y/n]?
At the prompt, type y and press Enter.
For details on configuring WinRM with default settings, refer to the Microsoft documentation.
To ensure that the collector system has access to the forwarder system
- On the forwarder system, open the Computer Management window.
In the left pane, expand System Tools > Local Users and Groups, and click Groups.
In the right pane, double-click Event Log Readers.
- On the Event Log Readers Properties window, on the General tab, click Add.
- On the Select Users, Computers, Service Accounts, or Groups dialog box:
In the Enter the object names to select field, enter the appropriate domain account name, and click Check Names.
Make sure that the account is validated in the domain network before you proceed.
Click Object Types.
On the Object Types dialog box, select the Computers check box, and click OK.
- In the Enter the object names to select field, enter the collector system name, and click Check Names.
Make sure that the system is validated in the domain network before you proceed.
- Click OK to save the changes and close the dialog box, and then close each of the windows opened for this procedure.
To set up the subscription on the collector system
- On the collector system, open the Event Viewer window.
- In the left pane, right-click Subscriptions and click Create Subscription.
- On the Subscription Properties window:
In the Subscription name field, provide an appropriate name for the InfoScale event collection subscription from the forwarder systems.
In the Destination Log dropdown list, select Forwarded Events.
In the Subscription type and source computers section, select Collector initiated and then click Select Computers.
In the collector-initiated subscription type, the collector system contacts the specified forwarder systems to collect event details. This subscription type works well in scenarios with a small, manageable number of forwarder systems.
- On the Computers dialog box, click Add Domain Computers.
- On the Select Computer dialog box, In the Enter the object name to select field, enter the forwarder system name, and click Check Names.
Make sure that the system is validated in the domain network before you proceed.
- Repeat steps 4 and 5 for each of the forwarder systems from which you want to collect the InfoScale event details.
- For each system in the Computers list on the left, click Test.
Make sure that the Event Viewer dialog box displays the Connectivity test succeeded message.
- Click OK to close the dialog boxes.
- On the Subscription Properties window, click Select Events.
- On the Query Filter window, set the various filters to narrow down the specific list of event details that you want the collector system to collect, and then click OK.
- On the Subscription Properties window, click Advanced.
- On the Advanced Subscription Settings dialog box:
Make sure that Machine Account is selected (default).
Select the Event Delivery Optimization option that is appropriate for the frequency of event details delivery as per your organization's needs.
- Click OK to save the changes and close the dialog box, and then close each of the windows opened for this procedure.
Henceforth, events for this subscription begin to appear under Event Viewer > Windows Logs > Forwarded Events, based on the filters set in step 10 and the frequency set in step 12.
- (Optional) Alternatively, on the Subscription Properties window, in the Subscription type and source computers section, you can select Source computer initiated and then click Select Computer Groups.
In the source computer-initiated subscription type, the forwarder systems contact the collector system to forward event details. This subscription type works well in scenarios with a large number of forwarder systems.
For details on creating the source computer-initiated subscription type, refer to the Microsoft documentation.