VxVM – vxdctl Command Syntax with Examples
Product – Veritas Volume Manager 6.0 (Storage Foundation)
/usr/sbin/vxdctl
- Manages aspects of the state of the volume configuration daemon ‘vxconfigd’.
- Sets default disk group for the system.
- Sets Boot Disk Group if the root disk is under VxVM Control.
- It uses ‘/etc/volboot’ file to manage default & boot disk groups. It also uses the host ID to establish ownership of physical disks.
Tasks |
Switches |
| Set Default Boot Diskgroup | vxdctl bootdg group |
| Set Default Diskgroup | vxdctl defaultdg diskgroup |
| Enable or disable command completion | vxdctl cmdcompletion enable|disable |
| Place ‘vxconfigd’ into ‘disabled’ mode for maintenance operations | vxdctl disable |
| Enable ‘vxconfigd’ to rebuild device node directories & DMP databases | vxdctl [-f] enable |
| Change the ‘hostid’ in volboot file | vxdctl hostid hostid |
| Reinitialize the volboot file | vxdctl init [hostid] |
| Recreate fresh nodes for DMP devices | vxdctl initdmp |
| List or Rescan VxVM licenses for usable features | vxdctl license [init] |
| Display ‘volboot’ file information | vxdctl list |
| Display or Set ‘vxconfigd’ log level(0-9) | vxdctl debug {[tagged=]level [pathname] | get} |
| Display Current Operating Mode | vxdctl [-c] mode |
| Print cluster protocol range supported by the node | vxdctl protocolrange |
| Print current cluster protocol version of the node | vxdctl protocolversion |
| Display or Set maximum number of threads available to process | vxdctl request_threads [count] |
| Display or Set Protocol version in ‘volboot’ file | vxdctl setversion [version] |
| Request ‘vxconfigd’ to exit | vxdctl [-k] stop |
| Displays versions of VxVM objects & components that are supported | vxdctl support |
| Displays the shared transaction status of the node | vxdctl transstate |
| Remove an attribute from the volboot file | vxdctl [-F] unset attribute |
| Upgrade cluster to the highest cluster protocol possible | vxdctl upgrade |
vxdctl – Examples
Set Default Boot Diskgroup
# vxdctl bootdg rootdgSet Default Diskgroup
# vxdctl defaultdg testdgEnable or disable command completion
# vxdctl cmdcompletion enable
VxVM vxdctl INFO V-5-2-0
Enabling command auto-completion feature with this interface will:
- Newly create .bash_profile, if it is not present.
- If .profile file exists, it will copy the contents of .profile to .bash_profile.
So user need to use .bash_profile as a default profile file.
- Persistently enable the feature with every login to bash shell.
If you don't wish to newly create .bash_profile, then you need to either reinvoke
bash shell or source /etc/bash_completion.d/vx_bash manually each time you login.
Do you want to continue? [y,n,q,?] (default: y) y
VxVM vxdctl INFO V-5-2-0 VxVM command auto-completion successfully enabled.
# vxdctl cmdcompletion disable
VxVM vxdctl INFO V-5-2-0 VxVM command auto-completion successfully disabled.Place ‘vxconfigd’ into ‘disabled’ mode for maintenance operations
# vxdctl disable
# vxprint -hvtg oradg
VxVM vxprint ERROR V-5-1-684 IPC failure: Configuration daemon is not accessibleEnable ‘vxconfigd’ to rebuild device node directories & DMP databases
# vxdctl enableChange the ‘hostid’ in volboot file
# vxdctl hostid s10u11.vxtestserverList VxVM licenses for usable features
# vxdctl license
All features are available:
Mirroring
Root Mirroring
Concatenation
Disk-spanning
Striping
RAID-5
RAID-5 Snapshot
VxSmartSync
Array Snapshot Integration Feature
FastResync
DGSJ
Site Awareness
DMP (multipath enabled)
CDS
Dynamic LUN Expansion
Hardware assisted copy
DMP Native SupportRe-scan VxVM licenses for usable features
# vxdctl license initDisplay ‘volboot’ file information
# vxdctl list
Volboot file
version: 3/1
seqno: 0.3
cluster protocol version: 120
hostid: vxserver
defaultdg: oradg
bootdg: rootdg
hostguid: {0a580b84-397b-11e4-a991-000c29656c89}Display or Set ‘vxconfigd’ log level(0-9)
# vxdctl debug get
loglevel: 0 taggedlevel: 0 logfile:Display Current Operating Mode
# vxdctl mode
mode: enabledPrint the cluster protocol range supported by the node
# vxdctl protocolrange
minprotoversion: 90, maxprotoversion: 120Print the current cluster protocol version of the node
# vxdctl protocolversionDisplay or Set maximum number of threads available to process
# vxdctl request_threads
2Display or Set Protocol version in ‘volboot’ file
# vxdctl setversion
100
# vxdctl setversion 120
# vxdctl setversion
120Displays the versions of VxVM objects and components that are supported
# vxdctl support
Support information:
vxconfigd_vrsn: 34
dg_minimum: 20
dg_maximum: 180
kernel: 33
protocol_minimum: 90
protocol_maximum: 120
protocol_current: 0Displays the shared transaction status of the node
# vxdctl transstate
transaction state: cluster inactive
hastatus
NAME
hastatus - display resource, group, and system attribute value changes, and monitor transitions
SYNOPSIS
hastatus [-sound] [[-group group] [-group group] . . . ]
hastatus [-sound] [[-sys system] [-sys system] . . . ]
hastatus [-sound] [[-resource resource] [-resource resource] . . . ]
hastatus -sum[mary]
hastatus -help
AVAILABILITY
VRTSvcs
DESCRIPTION
The hastatus command displays resource, group, and system attribute value changes, and monitors transitions. Also, if the Global Cluster option is is use, remote cluster, system, group, resource, and heartbeat information is displayed.
OPTIONS
[-sound] [[-group group] [-group group] . . . ]
Displays output in tabular format of the current state of all known systems and of the specified group and its resources (or all groups if no group is specified), and provides updates as they occur. The -sound option causes the bell to ring every time a resource faults.
[-sound] [[-sys system] [-sys system] . . . ]
Displays the status of all systems specified on the command line and shows the status of all groups and their resources on the specified systems. The specified systems are registered for updates on changes in status.
[-sound] [[-resource resource] [-resource resource] . . . ]
Displays the status of the groups associated with the specified resources on all systems. The specified resources and their associated groups are registered for updates in status on all systems.
-sum[mary]
Provide the current status of faults in the VCS cluster, including faulted service groups, resources, links, or agents.
-help
Displays usage message.
NOTES
The hastatus command (except for the summary option) may be started even if the VCS server is not running. It tries to connect every five seconds.
vxclustadm
NAME
vxclustadm - start, stop, and reconfigure a cluster
SYNOPSIS
vxclustadm abortnode
vxclustadm nidmap
vxclustadm [-v] nodestate
vxclustadm -m vcs reinit
vxclustadm -m vcs -t gab startnode
vxclustadm -m vcs -C cluster_name -t gab [-j join_timeout] startnode
vxclustadm stopnode
DESCRIPTION
The vxclustadm utility activates and deactivates cluster functionality on a node in a cluster.
Caution: Use of the clustering functionality of VxVM without a cluster monitor is not supported. Cluster reconfiguration problems may occur if there is no cluster monitor or if GAB is used as the cluster monitor. Ensure that you completely understand the functionality of this command before using it.
KEYWORDS
abortnode
Stops clustering activity on a node and abandons all uncompleted I/O on shared volumes. This command is for emergency shutdown.
nidmap
Prints a table showing the mapping between node IDs in VxVM's cluster-support subsystem and node IDs in the cluster monitor.
nodestate
Displays the state of a node in the cluster and the reason for last abort of the node on the standard output. Valid states are:
cluster aborting
The node is being aborted from the cluster.
cluster member
The node is a member of the cluster. All shared volumes in the cluster are accessible.
joining
The node is in the process of joining a cluster. It has been initialized but is not yet completely in the cluster. The node goes into this state after vxclustadm is executed with the startnode keyword.
out of cluster
The node is not joined to the cluster.
Refer to the Veritas Volume Manager Administrator's Guide for more information about reasons why a node may leave a cluster.
For debugging purposes the -v option can be specified to display the node ID, master ID, neighbor ID, current state, and reason for a node leaving the cluster (if appropriate).
reinit
The reinit keyword allows nodes to be added to or removed from a cluster dynamically without stopping the cluster. The command causes vxclustadm to re-read the cluster configuration file, and implement any required changes to the membership of the cluster.
The -m vcs option specifies the VCS cluster monitor, which implies the existence of the cluster configuration file, /etc/VRTSvcs/conf/config/main.cf.
startnode
The startnode keyword initiates cluster functionality on a node using the information supplied in the cluster configuration file. This is the first command that must be issued on a node to bring it into the cluster.
The argument to the -m option specifies the cluster monitor, which implies the existence of a cluster configuration file:
vcs
The cluster is running in the VCS environment. The cluster configuration file is /etc/VRTSvcs/conf/config/main.cf.
Caution: Use VCS commands to edit the main.cf file. Do not edit this file by hand.
startnode passes the information in the cluster configuration file to the VxVM kernel. In response to this command, the kernel and the VxVM configuration daemon, vxconfigd, perform the initialization.
The argument to the -t option specifies the protocol to be used for messaging:
gab
Use GAB as the transport agent for messaging in addition to using GAB as a cluster monitor. If you try to use GAB as a transport agent with a cluster monitor other than GAB (or outside the VCS environment), the kernel issues a warning message and changes the transport agent to UDP.
When the cluster is running in the VCS environment, the clustering functionality of VxVM should use GAB as the transport agent for messaging.
stopnode
Stops cluster functionality on a node, and waits for all outstanding I/O to complete and for all applications to close shared volumes or devices.
EXIT CODES
vxclustadm returns the following exit values:
2
Invalid state.
101
Node is not in cluster.
102
Node is joining the cluster, or is involved in reconfiguration.
103
Node is a cluster member.
104
Node is aborting from cluster.
FILES
For a cluster that is operating without a cluster monitor, or that is using GAB as the cluster monitor outside the VCS environment, and which is using UDP as its transport agent for messaging, the cluster configuration file, /etc/vx/cvmtab, contains the following fields:
clustername cluster_name
port vxconfigd port_number
port vxkmsgd port_number
node node_ID name name_on_local_net
timeout timeout_value
...
The recommended port numbers for the vxconfigd and vxkmsgd daemons are 4500 and 4501, but any available port numbers greater than 1024 are also acceptable.
name_on_local_net is the node's IP address or resolvable host name on the cluster's private network.
timeout_value is the timeout value in seconds. The clustering functionality of VxVM uses this value during cluster reconfiguration. The appropriate value to use depends on the number of nodes in the cluster and on the size of the shared disk group configuration. In most cases the value of 200 seconds is sufficient but this may need to be increased for larger configurations.
Comment lines in the file start with a #.
If GAB is being used as the transport agent for messaging, fields relating to port numbers and local network names are not required:
clustername cluster_name
node node_ID name
timeout timeout_value
...
For a cluster running in the VCS environment, VxVM obtains information about the cluster from the VCS cluster configuration file (/etc/VRTSvcs/conf/config/main.cf). Cluster-specific information may be appended to this file by running the vxcvmconfig command. For more information refer to the Veritas Cluster File System Installation and Configuration Guide.
EXAMPLES
A cluster consisting of four nodes, named node0, node1, node2 and node3, operates without a cluster monitor, and has the following cvmtab file when UDP is used as the transport agent for messaging:
# ClusterName
clustername CVM1
# Daemon port numbers
port vxconfigd 4500
port vxkmsgd 4501
# NodeID Nodename Localname
node 0 node0 node0_p
node 1 node1 node1_p
node 2 node2 node2_p
node 3 node3 node3_p
# Timeout value
timeout 200
If GAB is used as the transport agent for messaging, the cvmtab file only needs to contain the following information:
# ClusterName
clustername CVM1
# NodeID Nodename
node 0 node0
node 1 node1
node 2 node2
node 3 node3
# Timeout value
timeout 200
If node1 is the first node to join the cluster, it becomes the master node. The following command confirms that node1 is the master node:
vxdctl -c mode
To determine if reconfiguration of node3 is complete, examine the value returned from running the following command on node3:
vxclustadm -v nodestate
To confirm that node3 is a slave node, the following command is run on node3:
vxdctl -c mode
node1 remains as the master node for its lifetime in the cluster. To remove node1 from the cluster, the following command is run on node1:
vxclustadm stopnode
NOTES
vxclustadm does not ensure the consistency of cluster membership information.
gabconfig
NAME
gabconfig - Group Membership and Atomic Broadcast (GAB) configuration utility
SYNOPSIS
sbin/gabconfig [-abcejklsuUvx] [-f iofence] [-h interval] [-m count] [-n count ] [-t stable ]
DESCRIPTION
The gabconfig utility sets up and maintains the configuration of the GAB driver. The GAB driver is dependent on the Low Latency Transport (LLT) protocol, which must be configured prior to running gabconfig.
OPTIONS
-a
Display GAB driver port memberships.
-b
Enable system halt when the process fails to heartbeat. By default, if a process fails to heartbeat in a given interval, GAB makes five attempts to kill the process. With this option set, GAB panics the system without making any attempts to kill the process. Note that this option cannot be turned off once set.
-e
Print out kernel tunables set for GAB. If the value of the tunables is changed, the changed value will get into effect on module reload.
-c
Configure the driver for use. Configuring the GAB driver enables client registrations and the joining of an already seeded group.
-j
Enable halt on rejoin. A network failure may cause systems to form independant clusters, or partitions. When the connections are restored, systems will attempt to rejoin into one cluster. By default, GAB kills processes associated with ports on rejoining systems. This option directs GAB to halt the system.
-k
Repeat attempts to kill a process that does not die. By default, after five attempts to kill a process, GAB halts the system. This option directs GAB to close the client port and repeatedly and silently attempt to kill a process without halting the system.
-l
Display the GAB driver configuration.
-s
Single network. This flag disables network partition arbitration and should be used only to test configurations. It is required for operating GAB over one network connection with no alternative communication path, such as heartbeat disks.
-u
Unconfigure the GAB driver. Close the seed control port (port a) if all client ports are closed.
-U
Unconfigure the GAB driver and reinitialize all configuration states, including disk and seed configurations.
-v
Display GAB version information.
-x
Seed control port. This option affords protection from pre-existing network partitions. The control port (port a) propagates the seed to all configured systems. GAB must be seeded to enable the delivery of membership on client ports.
-f iofence_timeout
Specify a timeout (in milliseconds) for clients to respond to an IOFENCE message before the system halts. When clients receive an IOFENCE message, they must unregister from the GAB driver within iofence_timeout milliseconds to avoid halting the system. The default is 15000ms or 15 seconds.
-h heartbeat_interval
Disk heartbeating interval, in milliseconds. If heartbeat disks are configured, this parameter monitors connectivity through the disk. The default is 1000ms or 1 second.
-m disk_heartbeat_miss_count
The number of disk heartbeats that can be missed before the disk or path is declared unavailable. The default is 4.
-n system_count
Count of systems in the cluster. A non-zero system count auto-seeds the cluster when all systems are present. The default is zero, for no auto-seeding.
-t stable_timeout
Specifies the time GAB waits to reconfigure membership after the last report from LLT of a change in the state of local node connections for a given port. Any change in the state of connections will restart GAB waiting period. stable_timeout applies during membership transitions. The default value for stable_timeout is five seconds. Note that message latency for connection state messages, typically less than one second, should be taken into consideration when calculating stable_timeout value.
VxVM – vxdisk Command Syntax with Examples
/usr/sbin/vxdisk – Define and manage VERITAS Volume Manager disks
The vxdisk utility performs basic administrative operations on disks. Operations include initializing and replacing disks, as well as taking care of some book-keeping necessary for the disk model presented by VERITAS Volume Manager (VxVM).
[box type=”note” align=”alignleft” ]Note: A disk does not have a disk media name until it has been initialized by VxVM. For vxdisk operations on an initialized disk (disk), the disk may be specified either by its disk access name or by its disk media name.Physical disks in VxVM are assumed to be movable, and are usually identified by a unique disk ID stored on the physical disk, rather than by a disk device node. This allows disks to be moved to different SCSI target IDs or to different controllers without affecting correct operation.[/box]
| Tasks | Switches |
| Determine the usability of the specified disks | vxdisk [-f] [-g diskgroup] check disk |
| Clear the host-specific import information stored on the disks | vxdisk [-f] clearimport accessname … |
| Define disk access record, but do not initialize | vxdisk [-f] define accessname [attribute …] |
| Uninitializes a disk from VxVM | vxdisk [-f] destroy accessname … |
| Rewrite all CDS ID information to the specified disk | vxdisk [-f] flush accessname … |
| Initializes regions of a disk used by VxVM. | vxdisk [-f] [-r] init accessname [attribute …] |
| Display disk summary | vxdisk [-g diskgroup] list |
| Display detailed information about the specified disks | vxdisk [-g diskgroup] list accessname |
| Display OS native name based output | vxdisk [-g diskgroup] -e list |
| Display Disk summary information about specified disk | vxdisk [-g diskgroup] -s list [accessname] |
| Display discovery information about disks | vxdisk [-g diskgroup] -p list [accessname] |
| Customized discovery information | vxdisk [-x name1 -x name2] -p list |
| Display all disk association information | vxdisk -o alldgs list |
| Take the disk offline | vxdisk [-f] [-l filename] offline [accessname …] |
| Bring the disk’s to online | vxdisk [-f] [-a] [-l filename] online [accessname …] |
| Resize Disks or LUNS | vxdisk [-f] [-g diskgroup] resize {accessname|medianame} [length=value] |
| Remove disk from VxVM’s view | vxdisk [-f] rm accessname … |
| Initiates the rescanning of devices | vxdisk [-f] scandisks [ [!]device=…| [!]ctlr=…| [!]pctlr=…|new|fabric] |
| Updates the unique disk identifier | vxdisk [-g diskgroup] updateudid disk … |
Determine the usability of the specified disks
# vxdisk check c3t1d0
c3t1d0: Error: Disk is not usable
# vxdisk check c3t2d0
c3t1d0s2: OkayClear the host-specific import information stored on the indicated disks
Example scenario,
[box type=”error” align=”alignleft” ]VxVM vxdg ERROR V-5-1-10978 Disk group testdg: import failed: Disk is in use by another host[/box]
# vxdisk -f clearimport c3t1d0 c3t2d0Define disk access record, but do not initialize
# vxdisk define c4t13d0 format=cdsdisk DEVICE TYPE DISK GROUP STATUS
c4t13d0s2 auto:cdsdisk - - error
Device: c4t13d0s2
devicetag: c4t13d0
type: auto
info: format=cdsdisk,privoffset=256,pubslice=2,privslice=2
flags: error private
pubpaths: block=/dev/vx/dmp/c4t13d0s2 char=/dev/vx/rdmp/c4t13d0s2
guid: -
udid: -
site: -
errno: Disk is not useable, bad format
Multipathing information:
numpaths: 1
c4t13d0s2 state=enabledUn-initializes a disk from VxVM
DEVICE TYPE DISK GROUP STATUS
c4t13d0s2 auto:cdsdisk - - online
# vxdisk destroy c4t13d0
DEVICE TYPE DISK GROUP STATUS
c4t13d0s2 auto:none - - online invalidRewrite all CDS ID information to the specified disk
# vxdisk -f flush c4t13d0Initializes regions of a disk used by VxVM.
DEVICE TYPE DISK GROUP STATUS
c4t13d0s2 auto:cdsdisk - - error
# vxdisk -f init c4t13d0 format=cdsdisk
DEVICE TYPE DISK GROUP STATUS
c4t13d0s2 auto:cdsdisk - - onlineDisplay disk summary
# vxdisk list
DEVICE TYPE DISK GROUP STATUS
c1t0d0s2 auto:sliced rootdisk01 rootdg online
c2t0d0s2 auto:sliced rootdisk02 rootdg online
c3t1d0s2 auto:cdsdisk c3t1d0 testdg online
c3t2d0s2 auto:cdsdisk c3t2d0 testdg online
c3t3d0s2 auto:cdsdisk c3t3d0 testdg online nohotuse
c3t4d0s2 auto:cdsdisk c3t4d0 testdg online spare
c3t5d0s2 auto - - offline
c3t6d0s2 auto:cdsdisk disk1 newdg online
c4t10d0s2 auto:simple - - online
c4t11d0s2 auto:sliced - - online
c4t12d0s2 auto:none - - online invalid
c4t13d0s2 auto:cdsdisk - - error
c4t14d0s2 auto:none - - online invalid
- - disk2 newdg failed was:c4t9d0s2Display detailed information about the specified disks
# vxdisk list
Device: c3t1d0s2
devicetag: c3t1d0
type: auto
hostid: vxserver
disk: name=c3t1d0 id=1411575503.166.vxserver
group: name=testdg id=1411577705.178.vxserver
info: format=cdsdisk,privoffset=256,pubslice=2,privslice=2
flags: online ready private autoconfig autoimport imported
pubpaths: block=/dev/vx/dmp/c3t1d0s2 char=/dev/vx/rdmp/c3t1d0s2
guid: {68391d66-4406-11e4-a991-000c29656c89}
udid: VMware%2C%5FVMware%20Virtual%20S%5FDISKS%5F6000C299459294E7CD53E0D3DEECC10C
site: -
version: 3.1
iosize: min=512 (bytes) max=2048 (blocks)
public: slice=2 offset=65792 len=2031232 disk_offset=0
private: slice=2 offset=256 len=65536 disk_offset=0
update: time=1411587144 seqno=0.27
ssb: actual_seqno=0.0
headers: 0 240
configs: count=1 len=48144
logs: count=1 len=7296
Defined regions:
config priv 000048-000239[000192]: copy=01 offset=000000 enabled
config priv 000256-048207[047952]: copy=01 offset=000192 enabled
log priv 048208-055503[007296]: copy=01 offset=000000 enabled
lockrgn priv 055504-055647[000144]: part=00 offset=000000
Multipathing information:
numpaths: 1
c3t1d0s2 state=enabledDisplay OS native name based output
# vxdisk -e list
DEVICE TYPE DISK GROUP STATUS OS_NATIVE_NAME ATTR
disk_0 auto:sliced rootdisk02 rootdg online c2t0d0s2 -
disk_1 auto:cdsdisk disk1 newdg online c3t6d0s2 -
disk_2 auto - - offline c3t5d0s2 -
disk_3 auto:sliced rootdisk01 rootdg online c1t0d0s2 -
disk_4 auto:cdsdisk c3t4d0 testdg online spare c3t4d0s2 -
disk_5 auto:cdsdisk c3t1d0 testdg online c3t1d0s2 -
disk_6 auto:cdsdisk c3t3d0 testdg online nohotuse c3t3d0s2 -
disk_7 auto:cdsdisk c3t2d0 testdg online c3t2d0s2 -
disk_8 auto:simple - - online c4t10d0s2 -
disk_9 auto:none - - online invalid c4t12d0s2 -
disk_10 auto:cdsdisk - - error c4t13d0s2 -
disk_11 auto:sliced - - online c4t11d0s2 -
disk_12 auto:none - - online invalid c4t14d0s2 -
- - disk2 newdg failed was:c4t9d0s2Display Disk summary information about specified disk
# vxdisk -s list c3t1d0s2
Disk: c3t1d0s2
type: auto
flags: online ready private autoconfig autoimport imported
guid: {68391d66-4406-11e4-a991-000c29656c89}
udid: VMware%2C%5FVMware%20Virtual%20S%5FDISKS%5F6000C299459294E7CD53E0D3DEECC10C
site: -
diskid: 1411575503.166.vxserver
dgname: testdg
dgid: 1411577705.178.vxserver
hostid: vxserver
info: format=cdsdisk,privoffset=256,pubslice=2,privslice=2
vxdisk -o mediatype listDisplay discovery information about disks
# vxdisk -p list c4t9d0s2
DISK : c4t9d0s2
DISKID : 1411587602.274.vxserver
VID : OPNFILER
UDID : OPNFILER%5FVIRTUAL-DISK%5FDISKS%5FOPNFILERUEWMXR-tkYE-EV5k
SCSI_VERSION : 4
REVISION : 0
PID : VIRTUAL-DISK
PHYS_CTLR_NAME : /iscsi
MEDIA_TYPE : hdd
LUN_SNO_ORDER : 12
LUN_SERIAL_NO : OPNFILERUEWMXR-tkYE-EV5k
LIBNAME : scsi3_jbod
DMP_DEVICE : c4t9d0
CAB_SERIAL_NO : DISKS
ATYPE : Disk
ARRAY_PORT_PWWN:
ANAME : Disk
TRANSPORT : iSCSI
ENCLOSURE_NAME : disk
DMP_SINGLE_PATH: /dev/rdsk/c4t9d0s2
NUM_PATHS : 1Customized discovery information
# vxdisk -x DMP_SINGLE_PATH -x NUM_PATHS -p list
DEVICE DMP_SINGLE_PATH NUM_PATHS
c1t0d0s2 1 /dev/rdsk/c1t0d0s2
c2t0d0s2 1 /dev/rdsk/c2t0d0s2
c4t9d0s2 1 /dev/rdsk/c4t9d0s2
c4t10d0s2 1 /dev/rdsk/c4t10d0s2
c4t11d0s2 1 /dev/rdsk/c4t11d0s2
c4t12d0s2 2 NULL
c4t13d0s2 2 NULL
c4t14d0s2 2 NULLDisplay all disk association information
# vxdisk -o alldgs list
DEVICE TYPE DISK GROUP STATUS
c1t0d0s2 auto:sliced rootdisk01 rootdg online
c2t0d0s2 auto:sliced rootdisk02 rootdg online
c3t1d0s2 auto:cdsdisk - (testdg) online
c3t2d0s2 auto:cdsdisk - (testdg) online
c3t3d0s2 auto:cdsdisk - (testdg) online
c3t4d0s2 auto:cdsdisk - (testdg) online
c3t5d0s2 auto:cdsdisk - - online
c3t6d0s2 auto:cdsdisk - - onlineTake the disk offline:
[box type=”note” align=”alignleft” ]This operation cannot be applied to disks that are members of an imported disk group[/box]
# cat /access_names.txt
c3t1d0s2
c3t2d0s2
c3t3d0s2
c3t4d0s2
# vxdisk -f -l /access_names.txt offline
DEVICE TYPE DISK GROUP STATUS
c3t1d0s2 auto - - offline
c3t2d0s2 auto - - offline
c3t3d0s2 auto - - offline
c3t4d0s2 auto - - offlineBring the disk’s to online
# vxdisk -f -l /access_names.txt online
DEVICE TYPE DISK GROUP STATUS
c3t1d0s2 auto:cdsdisk - - online
c3t2d0s2 auto:cdsdisk - - online
c3t3d0s2 auto:cdsdisk - - online
c3t4d0s2 auto:cdsdisk - - onlineRe-sizing Disks or LUNS
[box type=”note” align=”alignleft” ]
Note:
- If you dont specify the length, all additional usable space on the device is claimed. – If you shrink a LUN, you must specify the new length explicitly.
- Any volumes on the device should only be grown after the device itself has first been grown. Otherwise, storage other than the device may be used to grow the volumes, or the volume resize may fail if no free storage is available.
- Resizing should only be performed on devices that preserve data. Consult the array documentation to verify that data preservation is supported. – It is possible to resize LUNs that are online but not part of any disk group.
- Do not perform this operation when replacing a physical disk with a disk of a different size as data is not preserved. – Before reducing the size of a device, any volumes on the device should first be reduced in size or moved off the device.
- If the device that is being resized has the only valid configuration copy for a disk group, the -f option may be specified to forcibly resize the device.
- Resizing a device that contains the only valid configuration copy for a disk group can result in data loss if a system crash occurs during the resize.[/box]
TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0
dm disk1 c4t9d0s2 - 2031232 - - - -
dm disk2 c4t18d0s2 - 982672 - - - -
# vxdisk -f -g testdg resize disk2
TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0
dm disk1 c4t9d0s2 - 2031232 - - - -
dm disk2 c4t18d0s2 - 2031232 - - - -Removing disk from VxVM’s view
DEVICE TYPE DISK GROUP STATUS
c3t1d0s2 auto:cdsdisk - - online
c3t2d0s2 auto:cdsdisk - - online
c4t14d0s2 auto:none - - online invalid
c4t16d0s2 auto:none - - online invalid
# vxdisk rm c4t14d0s2
DEVICE TYPE DISK GROUP STATUS
c3t1d0s2 auto:cdsdisk - - online
c3t2d0s2 auto:cdsdisk - - online
c4t16d0s2 auto:none - - online invalidInitiates the re-scanning of devices
DEVICE TYPE DISK GROUP STATUS
c3t1d0s2 auto:cdsdisk - - online
c3t2d0s2 auto:cdsdisk - - online
# vxdisk scandisks
DEVICE TYPE DISK GROUP STATUS
c3t1d0s2 auto:cdsdisk - - online
c3t2d0s2 auto:cdsdisk - - online
c4t16d0s2 auto:none - - online invalidYou can also use the following to re-scan the disks.
# vxdisk scandisks new
# vxdisk scandisks fabric
# vxdisk scandisks ctlr=c1,c2
# vxdisk scandisks !device=c1t1d0,c2t1d0Updates the unique disk identifier
# vxdisk updateudid c4t18d0s2
# vxdisk list c4t18d0s2 | grep -i udid
udid: OPNFILER%5FVIRTUAL-DISK%5FDISKS%5FOPNFILERlEz1fa-xZaX-5wpw
VxVM – vxprint Command Syntax with Examples
Product – Veritas Volume Manager-vxvm (Storage Foundation)
“vxprint” command will displays the volume’s,plex’s and sub disk’s record information.
vxprint’s options |
|
Option |
Description |
| -A | Print all disk groups |
| -h | List record hierarchies |
| -r | Print Related information |
| -n | Restrict output to record names |
| -l | List all record information in a verbose format |
| -f | Use simple one line list format |
| -m | List all record information as a make description |
| -t | Use one-line format tailored for each record type |
| – q | Suppress output field header |
| -Q | Suppresses disk group header |
| -g diskgroup | Specify a disk group to print |
| -e pattern | List records that match this search pattern |
| -N | Display only SAN information. default is nonSan only |
| -S | Print configuration summary information |
| -u h|H|unit | Print sizes with user readable extensions |
Disk Media State’s |
|
STATE’s |
Description |
| FAILING | Disk media is failing. |
| LFAILED | The node does not have local access to the disk. The node is sending private region I/Os through the network to a remote node that has local access to the disk. |
| LMISSING | The disk was not discovered locally by DMP. The node does not have a corresponding DMP device for the disk. |
| LOCAL_FAILING | Disk is fenced off. |
| NODEVICE | Disk is not valid. |
| NOHOTUSE | Disk cannot be used for Hot Relocation. |
| REMOVED | Disk is being removed from disk group. |
| RESERVED | Disk is reserved. |
| SPARE | Disk is marked as a spare for disk group. |
| ST_SPARE | Disk is marked as spare for storage pool. |
| VOLATILE | Disk state is changing. |
Volume States |
|
State |
Description |
| CLEAN | The volume is not started (kernel state is DISABLED) and its plexes are synchronized. For a RAID-5 volume, its plex stripes are consistent and its parity is good. |
| ACTIVE | The volume has been started (kernel state is currently ENABLED) |
| EMPTY | The volume contents are not initialized. The kernel state is always DISABLED when the volume is EMPTY. |
| INVALID | The contents of an instant snapshot volume no longer represent a true point-in-time image of the original volume. |
| NEEDSYNC | The volume requires a resynchronization operation the next time it is started. For a RAID-5 volume, a parity resynchronization operation is required. |
| REPLAY | The volume is in a transient state as part of a log replay. A log replay occurs when it becomes necessary to use logged parity and data. This state is only applied to RAID-5 volumes. |
| SYNC | The volume is either in read-writeback recovery mode (kernel state is currently ENABLED) or was in read-writeback mode when the machine was rebooted (kernel state is DISABLED). |
Volume Kernel States |
|
| State |
Description |
| DETACHED | Maintenance is being performed on the volume. The volume cannot be read from or written to, but certain plex operations and ioctl function calls are accepted. |
| DISABLED | The volume is offline and cannot be accessed. |
| ENABLED | The volume is online and can be read from or written to. |
Plex States |
|
State |
Description |
| ACTIVE | 1. When the volume is started and the plex fully participates in normal volume I/O 2. When the volume is stopped as a result of a system crash and the plex is ACTIVE at the moment of the crash |
| CLEAN | When it is known to contain a consistent copy (mirror) of the volume contents and an operation has disabled the volume. As a result, when all plexes of a volume are clean, no action is required to guarantee that the plexes are identical when that volume is started. |
| DCOSNP | Data change object (DCO) plex attached to a volume can be used by a snapshot plex to create a DCO volume during a snapshot operation. |
| EMPTY | Volume creation sets all plexes associated with the volume to the EMPTY state to indicate that the plex is not yet initialized. |
| IOFAIL | When the vxconfigd daemon detects an uncorrectable I/O failure on an ACTIVE plex, it places the plex in the IOFAIL state to exclude it from the recovery selection process at volume start time. |
| LOG | The state of a dirty region logging (DRL) or RAID-5 log plex is always set to LOG. |
| OFFLINE | The vxmend off task indefinitely detaches a plex from a volume by setting the plex state to OFFLINE. |
| SNAPATT | A snapshot plex that is being attached by the snapstart operation, when the attach is complete, the state for the plex is changed to SNAPDONE. If the system fails before the attach completes, the plex and all of its subdisks are removed. |
| SNAPDIS | A snapshot plex that is fully attached. If the system fails before the attach completes, the plex is dissociated from the volume. |
| SNAPDONE | A snapshot plex is ready for a snapshot to be taken |
| SNAPTMP | The SNAPTMP plex state is used during a vxassist snapstart operation when a snapshot is being prepared on a volume. |
| STALE | A plex does not have the complete and current volume contents, that plex is placed in the STALE state. Also, if an I/O error occurs on a plex, the kernel stops using and updating the contents of that plex, and the plex state is set to STALE. |
| TEMP | Setting a plex to the TEMP state eases some plex operations that cannot occur in a truly atomic fashion. |
Plex Kernel States |
|
State |
Description |
| DETACHED | Maintenance is being performed on the plex. |
| DISABLED | The plex is offline and cannot be accessed. |
| ENABLED | The plex is online. A write request to the volume is reflected in the plex. A read request from the volume is satisfied from the plex. |
SubCache & SubDisk Modes |
|
State |
Description |
| DET | The subdisk has been detached. |
| DIS | The subdisk is disabled. |
| dS | The subdisk in a RAID5 plex has failed and the RAID5 volume is in degraded mode (d indicates that the subdisk is detached, and S indicates that its contents are stale). |
| ENA | The subdisk is usable. |
| FAIL | The subdisk has been detached in the kernel due to an error. |
| NDEV | The media record on which the subdisk is defined has no associated access record. |
| RCOV | The subdisk is part of a RAID5 plex and has stale content. |
| RLOC | The subdisk has failed and is waiting to be relocated. |
| RMOV | The media record on which the subdisk is defined has been removed from its disk access record by a utility. |
SubVolume Modes |
|
State |
Description |
| ENA | The subvolume is usable. |
| DIS | The subvolume is disabled. |
| IOFAIL | The subvolume has been detached in the kernel due to an error. |
Command output with Examples:
To Display VxVM configuration Summary:
# vxprint -S
Disk group: oradg
VOLUMES PLEXES SUBDISKS PLEXFREE SDFREE DISKS RVGS RLINKS STPOOLS VSET CACHES EXPORTS
3 5 6 0 0 4 0 0 0 0 0 0Display Disk Media Records:
# vxprint -d
Disk group: oradg
TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0
dm oradisk01 c3t1d0s2 - 4128288 - - - -
dm oradisk02 c3t2d0s2 - 4128288 - - - -
dm oradisk03 c2t9d0s2 - 2031232 - - - -
# vxprint -l oradisk03
Disk group: oradg
Disk: oradisk03
info: diskid=1408760143.38.vxserver1
assoc: device=c2t9d0s2 type=auto
flags: autoconfig
device: path=/dev/vx/dmp/c2t9d0s2
devinfo: publen=2031232 privlen=65536
mediatype: hddDisplay Disk Group Records:
# vxprint -G
TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0
dg oradg oradg - - - - - -
# vxprint -l oradg
Disk group: oradg
Group: oradg
info: dgid=1408715327.33.vxserver1
version: 180
alignment: 8192 (bytes)
detach-policy: global
dg-fail-policy: dgdisable
ioship: off
copies: nconfig=default nlog=default
devices: max=32767 cur=1
minors: >= 15000
cds=on
# vxprint -g oradg
TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0
dg oradg oradg - - - - - -
dm oradisk01 c3t1d0s2 - 4128288 - - - -
dm oradisk02 c3t2d0s2 - 4128288 - - - -
dm oradisk03 c2t9d0s2 - 2031232 - - - -
v oravol fsgen ENABLED 204800 - ACTIVE - -
pl oravol-01 oravol ENABLED 204800 - ACTIVE - -
sd oradisk01-01 oravol-01 ENABLED 204800 0 - - -Display Volume Records:
# vxprint -v
Disk group: oradg
TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0
v appsvol fsgen ENABLED 204800 - ACTIVE - -
v oravol fsgen ENABLED 204800 - ACTIVE - -
# vxprint -g oradg -t oravol
V NAME RVG/VSET/CO KSTATE STATE LENGTH READPOL PREFPLEX UTYPE
v oravol - ENABLED ACTIVE 204800 SELECT - fsgen
# vxprint -l oravol
Disk group: oradg
Volume: oravol
info: len=204800
type: usetype=fsgen
state: state=ACTIVE kernel=ENABLED cdsrecovery=0/0 (clean)
assoc: plexes=oravol-01
exports=(none)
policies: read=SELECT (round-robin) exceptions=GEN_DET_SPARSE
flags: closed writeback
logging: type=REGION loglen=0 serial=0/0 mapalign=0 maplen=0 nummaps=64 (disabled)
apprecov: seqno=0/0
recovery: mode=default
recov_id=0
device: minor=15000 bdev=274/15000 cdev=274/15000 path=/dev/vx/dsk/oradg/oravol
perms: user=root group=root mode=0600
guid: {cb16f2d8-2a6a-11e4-8488-000c299c547d}Display SubDisk Records:
# vxprint -s
Disk group: oradg
TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0
sd oradisk01-01 oravol-01 ENABLED 204800 0 - - -
sd oradisk03-01 appsvol-01 ENABLED 204800 0 - - -
# vxprint -l oradisk01-01
Disk group: oradg
Subdisk: oradisk01-01
info: disk=oradisk01 offset=0 len=204800
assoc: vol=oravol plex=oravol-01 (offset=0)
flags: enabled
device: device=c3t1d0s2 path=/dev/vx/dmp/c3t1d0s2 diskdev=273/130
mediatype: hddDisplay Plexes Related Records:
# vxprint -p
Disk group: oradg
TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0
pl appsvol-01 appsvol ENABLED 204800 - ACTIVE - -
pl oravol-01 oravol ENABLED 204800 - ACTIVE - -
# vxprint -l appsvol-01
Disk group: oradg
Plex: appsvol-01
info: len=204800
type: layout=CONCAT
state: state=ACTIVE kernel=ENABLED io=read-write
assoc: vol=appsvol sd=oradisk03-01
flags: complete
mediatype: hddDisplay Configuration records in Human readable format:(Display VXVM Object Size in MB/GB/KB)
# vxprint -hvt -u h -t oravol
Disk group: oradg
V NAME RVG/VSET/CO KSTATE STATE LENGTH READPOL PREFPLEX UTYPE
PL NAME VOLUME KSTATE STATE LENGTH LAYOUT NCOL/WID MODE
SD NAME PLEX DISK DISKOFFS LENGTH [COL/]OFF DEVICE MODE
SV NAME PLEX VOLNAME NVOLLAYR LENGTH [COL/]OFF AM/NM MODE
SC NAME PLEX CACHE DISKOFFS LENGTH [COL/]OFF DEVICE MODE
DC NAME PARENTVOL LOGVOL
SP NAME SNAPVOL DCO
EX NAME ASSOC VC PERMS MODE STATE
v oravol - ENABLED ACTIVE 100.00m SELECT oravol-03 fsgen
pl oravol-03 oravol ENABLED ACTIVE 100.00m STRIPE 2/64.00k RW
sv oravol-S01 oravol-03 oravol-L01 1 50.00m 0/0.00 2/2 ENA
sv oravol-S02 oravol-03 oravol-L02 1 50.00m 1/0.00 2/2 ENA
Note : Use {m - MB, g - GB, k-KB}Display Records in Line list format:
# vxprint -g oradg -f
TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0
dg oradg oradg - - - - - -
dm oradisk01 c3t1d0s2 - 4128288 - - - -
dm oradisk02 c3t2d0s2 - 4128288 - - - -
dm oradisk03 c2t9d0s2 - 2031232 - - - -
dm oradisk04 c3t3d0s2 - 4128288 - - - -
sd oradisk01-02 oravol-P03 ENABLED 102400 0 - - -
sd oradisk02-02 oravol-P02 ENABLED 102400 0 - - -
sd oradisk03-02 oravol-P01 ENABLED 102400 0 - - -
sd oradisk04-02 oravol-P04 ENABLED 102400 0 - - -
sv oravol-S01 oravol-03 ENABLED 102400 0 - - -
sv oravol-S02 oravol-03 ENABLED 102400 0 - - -
pl oravol-P01 oravol-L01 ENABLED 102400 - ACTIVE - -
pl oravol-P02 oravol-L01 ENABLED 102400 - ACTIVE - -
pl oravol-P03 oravol-L02 ENABLED 102400 - ACTIVE - -
pl oravol-P04 oravol-L02 ENABLED 102400 - ACTIVE - -
pl oravol-03 oravol ENABLED 204800 - ACTIVE - -
v oravol fsgen ENABLED 204800 - ACTIVE - -
v oravol-L01 fsgen ENABLED 102400 - ACTIVE - -
v oravol-L02 fsgen ENABLED 102400 - ACTIVE - -Display Cache Volumes:
# vxprint -C
Disk group: oradg
TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0
co cacheobj - ENABLED - - ACTIVE - -To display the names of all associated plexes:
# vxprint -n -p -e assoc
cachevol-01
oravol-P01
oravol-P02
oravol-P03
oravol-P04
oravol-03To display the names of all unassociated plexes:
# vxprint -n -p -e \!assocTo display all unassociated subdisks:
# vxprint -s -e \!assocTo Display related record to the specified object:
# vxprint -r cachevol
Disk group: oradg
TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0
dm oradisk02 c3t2d0s2 - 4128288 - - - -
v cachevol cacheobj ENABLED 40960 - ACTIVE - -
pl cachevol-01 cachevol ENABLED 40960 - ACTIVE - -
sd oradisk02-01 cachevol-01 ENABLED 40960 0 - - -
lltconfig
NAME
lltconfig - Low Latency Transport (LLT) Protocol configuration utility
SYNOPSIS
lltconfig -h
lltconfig -c [-f file]
lltconfig [-v ] [-C clusterid] [-n systemid] [-i low_high] [-x low_high] [-o]
lltconfig -t devtag -d device [-b link_type -s SAP -m mtu]
lltconfig [-u device_tag]
lltconfig -U
lltconfig -V
lltconfig [-T timer:value]
lltconfig [-F limit:value]
lltconfig -a list | flush | delete | set [system] [ device_tag] [ address]
lltconfig -K 0 | 1 | 10 | 2 | 20
lltconfig -E 0 | 1 | 3
lltconfig -A 0 | 1
DESCRIPTION
The lltconfig utility initializes and maintains the configuration of the LLT protocol stack. It is responsible for managing the STREAMS plumbing between the LLT protocol driver and the network drivers to which it is connected, as well as many internal protocol parameters.
At system startup, lltconfig reads the /etc/llttab file to determine the local system ID and network devices, links the drivers, checks if there is another node with the same node id and then sets parameter information into LLT and starts the protocol running.
The lltconfig command without options reports the running status of the LLT protocol. The lltconfig command listens for 5 seconds on each link to see if it can detect a duplicate node in the cluster. It detects a duplicate node it prints an error message and exits.
OPTIONS
-a list | flush | delete | set [system] [device_tag] [address]
Display or manipulate MAC addresses associated with specific
systems on specific network links. The option list displays the address table. flush deletes all automatically learned addresses. delete removes one address as specified by the systemid and the device_tag. set adds one address for the system with the systemid on the link specified by device_tag . address should consist of hexadecimal digits separated by colons (:) or dots (.), depending on the link type.
-b link_type
Choose the link type required: "ether."
-C
Set the clusterid. This option is needed only if more than one cluster is sharing network hardware being used by LLT. In this case, each cluster needs its own clusterid (or, alternately, a unique SAP), so that the clusters do not interfere with each other. Systems with different cluster ids cannot communicate with each other. The default cluster ID is 0.
-c
Configure the LLT protocol from the /etc/llttab file.
-d device
Configure a network interface link below LLT. This link is bound to the LLT SAP and is used to send heartbeats and data to other systems. device is the name of the network device; it may be followed by a colon (:) and an integer specifying which unit or PPA to attach to (for example, -d /dev/qfe:1 ).
-f
Specify an alternate configuration file to use instead of /etc/llttab . This option is valid only with the -c option.
-F limit:value
Query or change the values of the flow control limits. Valid values for limit are query , lowwater , highwater , window , ackval , sws , and linkburst . The limits are the low water mark, high water mark, and window size, respectively. The value is specified in number of packets, and is not used with the query option. The values should not be changed haphazardly, or the protocol may fail to operate.
-h
Display a help message and exit.
-i low-high
Set a range, low-high , of system ids valid for participation in the cluster. This command alters the limits of system ids that applications may use to prevent them from trying to communicate with non-existent systems. The default is to include 0-nn, where nn is the maximum supported systemid as determined by the kernel configuration.
-l
Used only with the -d option, this option specifies that the network link is to be used only as a last resort for sending data, although it is used to send heartbeats.
-m mtu
Specify the maximum transmission unit to use for packets on the network links. This number must be less than or equal to the lowest MTU of all the network links. The current default is 1500. Packets having a value greater than this number are submitted to LLT as fragments.
-n systemid
Set the systemid. systemid may be an integer in the range of valid systemids. It may also be a symbolic name, which is translated via /etc/llthosts to a systemid, or it may be a filename beginning with a slash (/), in which case the first word from the file is used as a symbolic name and translated via /etc/llthosts to a systemid. Systemids must be unique within a cluster. If LLT detects a configuration in which another system is using the same systemid, it disables the protocol until the system is rebooted.
-o
Override flag. Specify that values such as systemid need to be overwritten. It can also be used to force LLT to configure a link even if a duplicate node is detected.
-s sap
Specify the SAP to bind on the network links using DLPI. The current default is 0xCAFE.
-T timer:value
Query or change the values of the protocol timers. Valid values for timer are query , heartbeat , heartbeatlo , peerinact , peertrouble , oos , retrans , service , and arp . These timers (except for query) are the heartbeat, heartbeat on low priority links, peer inactivity, link inactivity, out-of-sequence, retransmit, service procedure, and address resolution protocol cache flush timers respectively. Use lltconfig -T query to display the current timer settings. value is specified in 1/100ths of a second, and is not used with the query option. The values should not be changed haphazardly, or the protocol may fail to operate.
-t device_tag
Used only with the -d option, this option specifies a tag used to identify a particular link in subsequent commands, and is displayed by lltstat(1M) .
-u device_tag
Unlink the LLT protocol from the network device indicated by device_tag .
-U
Unlink the LLT protocol from the all network devices.
-V
Print the LLT current and maximum supported protocol version information.
-v
Enable verbose output.
-x low-high
Set a range, low-high , of systemids not valid for participation in the cluster. This option alters the limits of systemids that applications may use to prevent attempts to communicate with non-existent systems.
-K 0|1|10|2|20
Set checksum mode.
When set to 1, LLT checksums each packet it sends to peer to guard against packet corruption on-the-wire. LLT will also offload checksum calculation to hardware if the underlying NIC supports it. In case checksum verification fails on the receiver LLT will drop that packet causing the sender to retransmit it.
Setting to 10 is same as setting to 1 except that LLT will strictly do checksums in software and will NOT offload checksumming to NIC even if it is capable of doing so.
When set to 2, LLT also checksums the whole data buffer submitted by the client to be verified by the peer before delivering it to peer-client. In case the checksum verification fails on the receiver, LLT will panic the machine. This is purposefully done to help in analysis of memory corruption from a crash dump.
Setting to 20 is same as setting to 2 except that LLT will strictly do checksums in software and will NOT offload checksumming to NIC even if it is capable of doing so.
Level 2 and level 20 checksums should only be used when diagnosing memory corruption under the advisement of the support center, since it does have the ability to panic the machine.
The default is 0 (no checksums) as LLT depends on the NIC's hardware to guarantee packet accuracy. Level 1 checksums may be enabled if the private network is suspected of packet corruption on-the-wire or in the NIC. There may be some tradeoff of peformance due to the CPU cycles needed to perform the checksum in addition to those performed by the NIC hardware.
Currently checksum offloading is only implemented on Linux and only for transmitting packets.
-E 0|1|3
Set trace level.
If set to 1 (the default), LLT will trace all events (upcalls, flow-control, link and connection state changes) in an internal circular buffer (called as trace buffer).
When set to 3, LLT will also trace packets that are received or transmitted. This has an overhead and may impact performance. Hence should be used only to debug.
Setting to 0 disables tracing.
-A 0|1
Enable strict source address checking.
If set to 1, LLT will check the source address of incoming packets and drop packets from unknown sources. When set to 0 this check is not performed.
This option is available only when UDP links are configured. For ethernet its a no-op.
ENVIRONMENT VARIABLES
LLT_LINK_TIMEOUT
lltconfig listens for 5 seconds on each link to detect if another node in the cluster has the same node id. To change the default value, set this environment variable to a value in seconds.
DISCLAIMER
When LLT and GAB are running under a cluster manager other than VCS, configure LLT and GAB as per the cluster manager's supplementary documentation on LLT and GAB. -f option is applicable only in VCS environment.
FILES
/etc/llttab
VXVM – vxtask command examples with syntax
/usr/sbin/vxtask – List and administer VERITAS Volume Manager Tasks
The vxtask utility performs basic administrative operations on VERITAS Volume Manager (VxVM) tasks that are running on the system. Operations include listing tasks (subject to filtering), modifying the state of a task (aborting, pausing, resuming), and modifying the rate of progress of a task. VERITAS Volume Manager Tasks represent long-term operations in progress on the system. Every task provides the time the operation started, the size and progress of the operation, and the operation’s state and rate of progress (throttle).
Tasks |
Switches |
| Listing VxVM Tasks | vxtask [-ahlpqr ] [-g dg_name [-g dg_name…]] [[-G dg_name] -v volume [-v volume…]] [-i taskid] list [taskid…] |
| Pausing VxVM Tasks | vxtask pause taskid |
| Resuming VxVM Tasks | vxtask resume taskid |
| Aborting VxVM Tasks | vxtask abort taskid |
| Monitoring VxVM Tasks | vxtask [-c count] [-t time] [-w wait_interval] [-ln ] monitor [taskid[taskid…]] |
| Changing parameters of VxVM Tasks | vxtask [-i taskid] set name=value taskid |
Option |
Description |
| -a | Limits the output to tasks in the aborting state. |
| -g disk group | Limits the listed tasks to diskgroup |
| -G | Distinguishes between volumes with the same name in different diskgroups |
| -h | Prints tasks hierarchically with a task’s child tasks following the parent task |
| -l | Prints tasks in long format. |
| -p | Limits the output to tasks in the paused state. |
| -q | Suppresses printing of column headings. |
| -r | Limits the output to tasks in the running state. |
| -v volume | Limits the output to tasks whose object is volume. |
Listing VxVM Tasks
# vxtask list
TASKID PTID TYPE/STATE PCT PROGRESS
184 - RELAYOUT/R 04.50% 0/3276800/147456 RELAYOUT oravol oradgPrint tasks in long format
# vxtask -l list
Task: 184 PAUSED
Type: RELAYOUT
Operation: RELAYOUT Vol oravol Dg oradg
Started: Tue Oct 07 20:51:56 2014
Throttle: 0
Throttle time: 0
Progress: 65.04%2131136 of 3276800 Blocks
Work time: 2 minutes, 33 seconds (01:22 remaining)Print Running Tasks
# vxtask -r list
TASKID PTID TYPE/STATE PCT PROGRESS
184 - RELAYOUT/R 65.04% 0/3276800/2131136 RELAYOUT oravol oradgPrint paused tasks
# vxtask -p list
TASKID PTID TYPE/STATE PCT PROGRESS
184 - RELAYOUT/P 65.04% 0/3276800/2131136 RELAYOUT oravol oradgSuppress printing of column headings
# vxtask -q list
184 - RELAYOUT/P 65.04% 0/3276800/2131136 RELAYOUT oravol oradgPause specified tasks in running state
# vxtask -r list
TASKID PTID TYPE/STATE PCT PROGRESS
184 - RELAYOUT/R 04.50% 0/3276800/147456 RELAYOUT oravol oradg
# vxtask pause 184
# vxtask -p list - List paused tasks
TASKID PTID TYPE/STATE PCT PROGRESS
184 - RELAYOUT/P 65.04% 0/3276800/2131136 RELAYOUT oravol oradgResume specified paused tasks
# vxtask -p list - List paused tasks
TASKID PTID TYPE/STATE PCT PROGRESS
184 - RELAYOUT/P 65.04% 0/3276800/2131136 RELAYOUT oravol oradg
# vxtask resume 184Abort any specified tasks
# vxtask abort 184Monitoring VxVM Tasks
One line summary (Count=10, Exit_time=60s
# vxtask -c 10 -t 60 monitor
TASKID PTID TYPE/STATE PCT PROGRESS
210 - RELAYOUT/R 21.30% 0/3276800/698112 RELAYOUT oravol oradg
210 - RELAYOUT/R 21.43% 0/3276800/702208 RELAYOUT oravol oradg
210 - RELAYOUT/R 21.49% 0/3276800/704256 RELAYOUT oravol oradg
210 - RELAYOUT/R 21.55% 0/3276800/706304 RELAYOUT oravol oradg
210 - RELAYOUT/R 21.62% 0/3276800/708352 RELAYOUT oravol oradg
210 - RELAYOUT/R 21.68% 0/3276800/710400 RELAYOUT oravol oradg
210 - RELAYOUT/R 21.74% 0/3276800/712448 RELAYOUT oravol oradg
210 - RELAYOUT/R 21.80% 0/3276800/714496 RELAYOUT oravol oradg
210 - RELAYOUT/R 21.87% 0/3276800/716544 RELAYOUT oravol oradg
210 - RELAYOUT/R 21.93% 0/3276800/718592 RELAYOUT oravol oradgLong listing (count=3)
# vxtask -c 3 -l monitor 210
Task: 210 RUNNING
Type: RELAYOUT
Operation: RELAYOUT Vol oravol Dg oradg
Started: Tue Oct 07 21:35:14 2014
Throttle: 0
Throttle time: 0
Progress: 56.17%1840448 of 3276800 Blocks
Work time: 30 seconds (0:23 remaining)
Task: 210 RUNNING
Type: RELAYOUT
Operation: RELAYOUT Vol oravol Dg oradg
Started: Tue Oct 07 21:35:14 2014
Throttle: 0
Throttle time: 0
Progress: 56.23%1842496 of 3276800 Blocks
Work time: 30 seconds (0:23 remaining)
Task: 210 RUNNING
Type: RELAYOUT
Operation: RELAYOUT Vol oravol Dg oradg
Started: Tue Oct 07 21:35:14 2014
Throttle: 0
Throttle time: 0
Progress: 56.29%1844544 of 3276800 Blocks
Work time: 30 seconds (0:23 rema
'> IT (Information Technology)' 카테고리의 다른 글
| LOT, lot, 산업 용어, 제조 단위 (0) | 2023.08.29 |
|---|---|
| Symcli, PowerMax, DellEMC, Storage, Symmatrix 명령어 (0) | 2023.08.11 |
| CFS, 인포스케일, Veritas infoscale (0) | 2023.08.08 |
| SRDF, SRDF/A session dropped write pending limit reached. host throttling is disabled, SRDF/A 세션 중단 이유 및 3가지 사례 (1) | 2023.07.25 |
| CISCO L3 스위치 L2스위치 점검 (4) | 2023.07.05 |