InfoScale™ 9.0 Cluster Server 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
- 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
InfoScale log file permissions
The following table lists the parameter values and the corresponding log file permissions that are applicable when those values are set. These values are applicable to all the InfoScale components.
Table: Tunable parameter values, file permissions, and behavior
Tunable parameter value | Log file permissions | Behavior |
---|---|---|
0 (default) | 600 | Update existing file permissions on upgrade. |
1 | 640 | Update existing file permissions on upgrade. |
2 | 644 | Update existing file permissions on upgrade. |
10 | 600 | Do not change existing file permissions on upgrade. |
11 | 640 | Do not change existing file permissions on upgrade. |
12 | 644 | Do not change existing file permissions on upgrade. |
See Setting log file permissions.
Table: VxFS tunable parameter
InfoScale component | Tunable parameter | Located in file |
---|---|---|
VxFS | eo_perm |
|
Use the following command to set this tunable parameter:
# /opt/VRTS/bin/vxtunefs -D eo_perm=<parameter_value>
You can also manually set the parameter value using the following command:
# cat /etc/vx/vxfssystem eo_perm <parameter_value>
After changing the permissions, restart the VxFS services, or reboot the system, for the changes to take effect.
Table: VxVM tunable parameter
InfoScale component | Tunable parameter | Located in file |
---|---|---|
VxVM | log_file_permissions |
|
Use the following command to set this tunable parameter:
# vxtune log_file_permissions <parameter_value>
After changing the permissions, restart the VxVM services, or reboot the system, for the changes to take effect.
Table: VCS tunable parameter
InfoScale component | Tunable parameter | Located in file |
---|---|---|
VCS | VCS_ENABLE_PUBSEC_LOG_PERM |
|
For VCS, you can add the tunable with an appropriate value in the following file:
For example, # export VCS_ENABLE_PUBSEC_LOG_PERM=1.
After changing the permissions, restart the VCS service for the changes to take effect.
Run the following commands sequentially:
# hastop -local
# hastart
Note:
If there are other components under VCS control, for example, VxCPServ and VxFEN, then a VCS restart is required for the log file permissions changes of those components to take effect.
Alternatively, reboot the system for the changes to take effect.
Table: VxCPServ tunable parameter
InfoScale component | Tunable parameter | Located in file |
---|---|---|
VxCPServ | VCS_ENABLE_PUBSEC_LOG_PERM |
|
After changing the permissions, stop and restart the vxcpserv
process for the changes to take effect.
If VxCPServ is configured under VCS control (if there is a VCS service group for VxCPServ), then restart VCS using the following commands sequentially:
# hastop -local
# hastart
Or, use # hastart -onenode, if the CP Server is configured in a single-node VCS cluster.
Alternatively, reboot the system for the changes to take effect.
Table: DBED tunable parameter
InfoScale component | Tunable parameter | Located in file |
---|---|---|
DBED | VCS_ENABLE_PUBSEC_LOG_PERM |
|
For example, # export VCS_ENABLE_PUBSEC_LOG_PERM=1.
After changing the permissions, restart the vxdbd
daemon for the changes to take effect.
To enable the vxdbd
daemon, run the following command:
# /opt/VRTS/bin/sfae_config enable
To disable the vxdbd
daemon, run the following command:
# /opt/VRTS/bin/sfae_config disable
Alternatively, reboot the system for the changes to take effect.
Table: IOM tunable parameter
Component | Tunable parameter | Located in file |
---|---|---|
IOM | log_file_permissions |
|
Use the following CPI command to set this tunable parameter:
# /opt/VRTSsfmh/bin/perl /opt/VRTSsfmh/bin/set_logfiles_permissions.pl --logfile_permission=<parameter_value>
After changing the permissions, restart the IOM services, or reboot the system, for the changes to take effect.