![]() Hagrp -modify groupw SystemList sun1 1 sun2 2 sun3 3 Hagrp -modify groupw SystemList sun1 1 sun2 2 Hacf -cmdtocf /tmp -dest /etc/VRTSvcs/conf/config Hacf -cftocmd /etc/VRTSvcs/conf/config -dest /tmpĬonvert a command file into a main.cf file Note: you can point to any directory as long as it has main.cf and types.cfĬonvert a main.cf file into cluster commands When the configuration is putīack into read only mode the. stale file is created in $VCS_CONF/conf/config. When in read/write mode theĬonfiguration becomes stale, a. The VCS configuration must be in read/write mode in order to make changes. Unfreeze a system ( reenable groups and resource back online) System Operations add a system to the clusterĭisplay the value of a systems nodeid (/etc/llthosts)įreeze a system (No offlining system, No groups onlining) Stop the cluster on all nodes but leave the application/s runningĬluster Details information about a cluster Stop cluster on local server but evacuate (failover) the application/s to another node within the cluster Stop the cluster on the local server but leave the application/s running, do not failover the application/s “-force” instructs the engine to treat a stale config as a valid oneīring the cluster into running mode from a stale state using the configuration file from a particular server Starting and Stopping the cluster “-stale” instructs the engine to treat the local config as stale VCSMM driver (kernel module needed for Oracle and VCS interface).H VCS (VERITAS Cluster Server: high availability daemon) Override the seed values in the gabtab fileī I/O fencing (designed to guarantee data integrity) ![]() Note: port a indicates that GAB is communicating, port h indicates that VCS is started Lists information about each configured LLT link LLT and GAB Commands Verifying that links are active for LLTĭisplay the values of LLT configuration directives The file contains the information that defines the cluster and its systems. This file is used by the gabconfig utility. ![]() The file contains the information needed to configure the GAB driver. The file contains information that is derived during installation and is used by the utility lltconfig. The file is identical on each server in the cluster. The file is a database, containing one entry per system, that links the LLT system ID with the hosts name. The system admin configures GAB driver by creating a configuration file ( gabtab). GAB (Group membership and Atomic Broadcast) provides the global message order required to maintain a synchronised state among the systems, and monitors disk comms such as that required by the VCS heartbeat utility. The LLT runs in layer 2 of the network stack The system admin configures the LLT by creating a configuration file (llttab) that describes the systems in the cluster and private network links among them. LLT (Low Latency Transport) provides fast, kernel-to-kernel comms and monitors network connections. These components provide the performance and reliability required by VCS. VCS uses two components, LLT and GAB to share data over the private networks among systems. Tirathsingh on Essential DBA Interview Q… Sachin Thapa on Essential DBA Interview Q… Interview questions… on Essential DBA Interview Q… This could happen due to invalid configuration. FRM-92101: There was a failure in the Forms Server during startup.Difference between SYS and SYSTEM users.100k views Thanks everyone Happy learning. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |