InfoScale™ 9.0 Cluster Server Administrator's Guide - AIX
- 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
- 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. 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 VI. 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
- VCS message logging
- VCS performance considerations
- Section VII. Appendixes
Setting custom permissions for InfoScale log files
InfoScale provides tunable parameters that let you modify the log file permissions as needed. You can set the custom permissions during an upgrade using the installer or post-upgrade using the component-specific tunable parameters.
Each InfoScale component has a unique tunable parameter to which you can assign a value to set the desired log file permissions for that component. You can do this manually using the relevant commands or by directly editing the individual component's configuration file.
Note:
When you set the permissions manually, you must restart the individual component service for the changes to take effect.
The log file permissions are set to the value that you provide, irrespective of whether you set the value during an upgrade or after the upgrade.
See Custom permissions for InfoScale log files.
To set log file permissions during upgrade
- When you upgrade an InfoScale product, the installer prompts you as follows:
Do you want to set the permission of the files as per EO logging standards? [y,n,q]
Enter y (Yes). The following prompt appears:
Please provide the proper permission option [b,q,?] (0)
- Enter ? to identify which value to use for a specific permission. The following options are displayed:
0 (default) - 600 permissions, update existing file permissions on upgrade 1 - 640 permissions, update existing file permissions on upgrade 2 - 644 permissions, update existing file permissions on upgrade 10 - 600 permissions, don't touch existing file permissions on upgrade 11 - 640 permissions, don't touch existing file permissions on upgrade 12 - 644 permissions, don't touch existing file permissions on upgrade
Please provide the proper permission option [b,q,?] (0)
Enter a value from these available options to set the required permissions. For example, enter 10 to set the permissions of all the new log files to the default value of 600 (read-write access to owner), but not change any existing log file permissions.
Note that this value gets applied to all the InfoScale log files. Post upgrade, you can use the manual method to set permissions for log files at an individual component level.
Enter q at the prompt when you finish changing the file permissions as per your needs.
If you do not specify a value, 0 (zero) is considered as the default.
To set log file permissions after upgrade
- Use the appropriate command to set the component-specific tunable parameter.
For VxFS:
To directly set the parameter value, run:
# /opt/VRTS/bin/vxtunefs -D eo_perm=<parameter_value>
To edit the parameter value in the configuration file, run:
# cat /etc/vx/vxfssystem eo_perm <parameter_value>
For VxVM:
To directly set the parameter value, run:
# vxtune log_file_permissions <parameter_value>
For VCS:
To add the value in the
/opt/VRTSvcs/bin/vcsenv
file, run:# export VCS_ENABLE_PUBSEC_LOG_PERM=1
Note:
If there are other components under VCS control, for example, VxCPServ and VxFEN, then a VCS restart is also required for the log file permissions changes of those components to take effect.
For VxCPServ:
Add the VCS_ENABLE_PUBSEC_LOG_PERM=1 parameter value to the
/etc/vxcps.conf
file.For SFDB tools (DBED):
To add the value in the
/etc/vx/vxdbed/dbedenv
file, run:# export VCS_ENABLE_PUBSEC_LOG_PERM=1
For InfoScale Operations Manager:
To edit the
/etc/opt/VRTSsfmh/log_file_permissions.conf
configuration file, run:# /opt/VRTSsfmh/bin/perl /opt/VRTSsfmh/bin/set_logfiles_permissions.pl --logfile_permission=<parameter_value>
- Either restart the component-specific services or restart the system for the changes to take effect.
In case of a coordination point server (CP server) configuration under VCS control, stop and restart the
vxcpserv
process using the hastop and hastart commands locally.In case of a CP server configuration in a single-node VCS cluster, use the hastart -onenode command.
In case of SFDB tools, to restart the
vxdbd
daemon, run:# /opt/VRTS/bin/sfae_config disable
# /opt/VRTS/bin/sfae_config enable