Veritas Cluster Quick Reference
1. Starting and Stopping the Cluster
"-stale" instructs the engine to treat the local config as stale "-force" instructs the engine to treat a stale config as a valid one | hastart [-stale|-force] |
Bring the cluster into running mode from a stale state using the configuration file from a particular server | hasys -force |
Stop the cluster on the local server but leave the application/s running, do not failover the application/s | hastop -local |
Stop cluster on local server but evacuate (failover) the application/s to another node within the cluster | hastop -local -evacuate |
Stop the cluster on all nodes but leave the application/s running | hastop -all -force |
Display cluster summary | hastatus -summary |
Continually monitor cluster | hastatus |
Verify the cluster is operating | hasys -display |
Information about a cluster | haclus -display |
Value for a specific cluster attribute | haclus -value |
Modify a cluster attribute | haclus -modify |
Enable LinkMonitoring | haclus -enable LinkMonitoring |
Disable LinkMonitoring | haclus -disable LinkMonitoring |
Add a user | hauser -add |
Modify a user | hauser -update |
Delete a user | hauser -delete |
Display all users | hauser -display |
Add a system to the cluster | hasys -add |
Delete a system from the cluster | hasys -delete |
Modify a system attributes | hasys -modify |
List a system state | hasys -state |
Force a system to start | hasys -force |
Display the systems attributes | hasys -display [-sys] |
List all the systems in the cluster | hasys -list |
Change the load attribute of a system | hasys -load |
Display the value of a systems nodeid (/etc/llthosts) | hasys -nodeid |
Freeze a system (No offlining system, No groups onlining) | hasys -freeze [-persistent][-evacuate] Note: main.cf must be in write mode |
Unfreeze a system ( reenable groups and resource back online) | hasys -unfreeze [-persistent] Note: main.cf must be in write mode |
The VCS configuration must be in read/write mode in order to make changes.
When in read/write mode the configuration becomes stale, a .stale file is created in $VCS_CONF/conf/config.
When the configuration is put back into read only mode the .stale file is removed.
Change configuration to read/write mode | haconf -makerw |
Change configuration to read-only mode | haconf -dump -makero |
Check what mode cluster is running in | haclus -display |grep -i 'readonly' 0 = write mode |
Check the configuration file | hacf -verify /etc/VRTS/conf/config Note: you can point to any directory as long as it has main.cf and types.cf |
Convert a main.cf file into cluster commands | hacf -cftocmd /etc/VRTS/conf/config -dest /tmp |
Convert a command file into a main.cf file | hacf -cmdtocf /tmp -dest /etc/VRTS/conf/config |
Add a service group | haconf -makerw |
Delete a service group | haconf -makerw |
Change a service group | haconf -makerw Note: use the "hagrp -display |
List the service groups | hagrp -list |
List the groups dependencies | hagrp -dep |
List the parameters of a group | hagrp -display |
Display a service group's resource | hagrp -resources |
Display the current state of the service group | hagrp -state |
Clear a faulted non-persistent resource in a specific grp | hagrp -clear |
Change the system list in a cluster | # remove the host # add the new host (don't forget to state its position) # update the autostart list |
Start a service group and bring its resources online | hagrp -online |
Stop a service group and takes its resources offline | hagrp -offline |
Switch a service group from system to another | hagrp -switch |
Enable all the resources in a group | hagrp -enableresources |
Disable all the resources in a group | hagrp -disableresources |
Freeze a service group (disable onlining and offlining) | hagrp -freeze note: use the following to check "hagrp -display |
Unfreeze a service group (enable onlining and offlining) | hagrp -unfreeze note: use the following to check "hagrp -display |
Enable a service group. Enabled groups can only be brought online | haconf -makerw Note to check run the following command "hagrp -display | grep Enabled" |
Disable a service group. Stop from bringing online | haconf -makerw Note to check run the following command "hagrp -display | grep Enabled" |
Flush a service group and enable corrective action. | hagrp -flush |
Add a resource | haconf -makerw |
Delete a resource | haconf -makerw |
Change a resource | haconf -makerw Note: list parameters "hares -display |
Change a resource attribute to be globally wide | hares -global |
Change a resource attribute to be locally wide | hares -local |
List the parameters of a resource | hares -display |
List the resources | hares -list |
List the resource dependencies | hares -dep |
Online a resource | hares -online |
Offline a resource | hares -offline |
Display the state of a resource( offline, online, etc) | hares -state |
Display the parameters of a resource | hares -display |
Offline a resource and propagate the command to its children | hares -offprop |
Cause a resource agent to immediately monitor the resource | hares -probe |
Clearing a resource (automatically initiates the onlining) | hares -clear |
Add a resource type | hatype -add |
Remove a resource type | hatype -delete |
List all resource types | hatype -list |
Display a resource type | hatype -display |
List a partitcular resource type | hatype -resources |
Change a particular resource types attributes | hatype -value |
Add a agent | pkgadd -d . |
Remove a agent | pkgrm |
Change a agent | n/a |
List all ha agents | haagent -list |
Display agents run-time information i.e has it started, is it running? | haagent -display |
Display agents faults | haagent -display |grep Faults |
Start an agent | haagent -start |
Stop an agent | haagent -stop |
VCS uses two components, LLT and GAB to share data over the private networks among systems.
These components provide the performance and reliability required by VCS.
LLT | LLT (Low Latency Transport) provides fast, kernel-to-kernel comms and monitors network connections. 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. The LLT runs in layer 2 of the network stack |
GAB | 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 system admin configures GAB driver by creating a configuration file (gabtab). |
/etc/llthosts | The file is a database, containing one entry per system, that links the LLT system ID with the hosts name. The file is identical on each server in the cluster. |
/etc/llttab | The file contains information that is derived during installation and is used by the utility lltconfig. |
/etc/gabtab | The file contains the information needed to configure the GAB driver. This file is used by the gabconfig utility. |
/etc/VRTSvcs/conf/config/ main.cf | The VCS configuration file. The file contains the information that defines the cluster and its systems. |
/sbin/gabdiskconf - i /dev/dsk/c1t2d0s2 -s 16 -S 1123 |
gabdiskconf | -i Initialises the disk region |
gabdiskhb (heartbeat disks) | -a Add a gab disk heartbeat resource |
gabconfig | -c Configure the driver for use |
Verifying that links are active for LLT | lltstat -n |
Verbose output of the lltstat command | lltstat -nvv | more |
Open ports for LLT | lltstat -p |
Display the values of LLT configuration directives | lltstat -c |
Lists information about each configured LLT link | lltstat -l |
List all MAC addresses in the cluster | lltconfig -a list |
Stop the LLT running | lltconfig -U |
Start the LLT | lltconfig -c |
Verify that GAB is operating | gabconfig -a Note: port a indicates that GAB is communicating, port h indicates that VCS is started |
Stop GAB running | gabconfig -U |
Start the GAB | gabconfig -c -n |
Override the seed values in the gabtab file | gabconfig -c -x |
List Membership | gabconfig -a |
Unregister port f | /opt/VRTS/bin/fsclustadm cfsdeinit |
Port Function | a gab driver |
High Availability Daemon | had |
Companion Daemon | hashadow |
Resource Agent daemon | |
Web Console cluster managerment daemon | CmdServer |
Log Directory | /var/VRTSvcs/log |
Primary log file (engine log file) | /var/VRTSvcs/log/engine_A.log |
No comments:
Post a Comment