Here we will get some basic Idea of..
- VOLUME MANAGER RUNNING PROCESSES
- VXVM PATH
- VXVM INSTALL LOGS
- VXVM PACKAGE INFO
- N COLUMNS & ST WIDTH
- DG VERSION
- VXSTAT
- VXTRACE
- VXTASK
- VXNOTIFY
- VXVM CONFIGURATION DATABASE
- DISPLAYING HEADER INFO / DUMP PRIVATE REGION
- VXVM DAEMONS
- VXVM LOG
- VXVM DEBUG
- HOST ID
- DG BACKUP
- ALL COMMANDS LOG
- VOLD LOG
- IMPORTED DG INFO
- VXVM LOGGING
- TROUBLESHOOTING FILES / TOOLS
- DEBUGGING TOOLS ARE LOCATED AT
- VXVM EXPLORER
To confirm that the
Volume Manager processes (
vxconfigd, vxnotify, and vxrelocd) are running, use:
root@pr01:>/#
ps -e |grep vx
606 ? 0:03 vxesd
3775 ? 0:00 vxsvc
4606 ? 0:00 vxconfig
2878 ? 0:00 vxrelocd
2879
? 0:00 vxattach
3798 ? 0:01 vxrelocd
2430 ? 0:00 vxdbd
2882 ? 0:00 vxconfig
3694 ? 0:00 vxattach
3802 ? 0:00 vxnotify
8807 ? 0:17 vxconfig
3698 ? 0:00 vxnotify
4607 ? 0:00 vxnotify
root@pr01:>/#
pkginfo -l |grep -i vxvm
NAME:
Oracle Solaris Cluster VxVM Support
DESC:
Oracle Solaris Cluster support for vxvm volume manager
PKGINST:
VRTSvxvm
PATH:-----------------
/opt/VRTS/bin
/opt/VRTS/man
VIEWING INSTALL LOGS:-----------------------
/opt/VRTS/install/logs
PKG INFO:--------------------
root@pr01:>/#
pkginfo -l VRTSvxvm
PKGINST:
VRTSvxvm
NAME:
Binaries for VERITAS Volume Manager by Symantec
CATEGORY:
system
ARCH:
i386
VERSION:
6.0.100.000,REV=08.01.2012.11.29
BASEDIR:
/
VENDOR:
Symantec Corporation
DESC:
Virtual Disk Subsystem
PSTAMP:
6.0.100.000-GA-2012-08-01
INSTDATE:
Nov 02 2016 17:57
HOTLINE:
http://www.symantec.com/business/support/assistance_care.jsp
STATUS:
completely installed
FILES:
841 installed pathnames
41 shared pathnames
116 directories
346 executables
425545 blocks used (approx)
root@pr01:>/#
pkginfo |grep -i vrts
system VRTSamf Veritas Asynchronous
Monitoring Framework Module
system VRTSaslapm Array Support Libraries
and Array Policy Modules for Veritas Volume Manager
optional VRTScps Veritas Co-ordination
Point Server by Symantec
application
VRTSdbed Veritas
Storage Foundation for Databases by Symantec
system VRTSfssdk Veritas File System
Software Developer Kit by Symantec
system VRTSgab Veritas Group
Membership and Atomic Broadcast by Symantec
system VRTSllt Veritas Low Latency
Transport by Symantec
application
VRTSob Veritas Enterprise Administrator Service
by Symantec
system VRTSodm Veritas Oracle Disk
Manager by Symantec
optional VRTSperl Perl 5.14.2 for
Veritas
optional VRTSsfcpi601 Veritas Storage Foundation Installer
application
VRTSsfmh Veritas
Operations Manager Managed Host by Symantec
application
VRTSspt Veritas
Software Support Tools by Symantec
optional VRTSvbs Virtual Business Services by
Symantec
system VRTSvcs Veritas Cluster
Server by Symantec
system VRTSvcsag Veritas Cluster Server
Bundled Agents by Symantec
system VRTSvcsea Veritas High Availability
Enterprise Agents by Symantec
application
VRTSvlic Symantec
License Utilities
system VRTSvxfen Veritas I/O Fencing by
Symantec
system VRTSvxfs Veritas File System by Symantec
system VRTSvxvm Binaries for VERITAS
Volume Manager by Symantec
root@pr01:>/#
root@pr01:>/#
root@pr01:>/#
pkginfo |grep -i veritas
system VRTSamf Veritas Asynchronous
Monitoring Framework Module
system VRTSaslapm Array Support Libraries
and Array Policy Modules for Veritas Volume Manager
optional VRTScps Veritas Co-ordination
Point Server by Symantec
application
VRTSdbed Veritas
Storage Foundation for Databases by Symantec
system VRTSfssdk Veritas File System
Software Developer Kit by Symantec
system VRTSgab Veritas Group Membership
and Atomic Broadcast by Symantec
system VRTSllt Veritas Low Latency
Transport by Symantec
application
VRTSob Veritas
Enterprise Administrator Service by Symantec
system VRTSodm Veritas Oracle Disk Manager by
Symantec
optional VRTSperl Perl 5.14.2 for
Veritas
optional VRTSsfcpi601 Veritas Storage Foundation
Installer
application
VRTSsfmh Veritas
Operations Manager Managed Host by Symantec
application
VRTSspt Veritas
Software Support Tools by Symantec
system VRTSvcs Veritas Cluster
Server by Symantec
system VRTSvcsag Veritas Cluster Server Bundled Agents by
Symantec
system VRTSvcsea Veritas High
Availability Enterprise Agents by Symantec
system VRTSvxfen Veritas I/O Fencing by
Symantec
system VRTSvxfs Veritas File System by
Symantec
system VRTSvxvm Binaries for VERITAS
Volume Manager by Symantec
root@pr01:>/#
N COLUMNS:-------------------------------------
There are
4 sd’s and need 1 column per sd.
ncol=4
need 2
columns , 2 sd’s / column
ncol=2
min no of
ncol in a volume is 2 and max is 8.
These can
be edited by defining
min_columns
& max_columns in /etc/default/vxassist file
stwidth =
stripe width
stripeunit=
size specifies the stripe unit to be
used (default is 64k)
4 subdisks
……………… ncol & sdwidth
Why ??
The data
should stretched on all 4 disks so that all 4 can share data load. In order to
do that we need to tell veritas how to
divide data. We do this by dividing data in to chunks which is specified by
“stwidth/stripeunit” and by sequentially
placing on different disks. Which is specified by “ncolumns”. So by defining
“ncol=4” the first 32k (stwidth=32k) will written to d1-01
1st 32k written to d1-01
2nd
32k written to d2-01
3rd
32k written to d3-01
4th
32k written to d4-01
5th
chunk goes back to d1-01
In this
way a single 128k data will exists on 4 disks, so Stripe Width is the amount of data that
should be written to a column before moving to the next and Column is the no of
subdisks to be written to.
root@pr01:>/#
vxdefault list
KEYWORD CURRENT-VALUE DEFAULT-VALUE
autostartvolumes on on
fssmartmovethreshold 100 100
reclaim_on_delete_start_time 22:10 22:10
reclaim_on_delete_wait_period 1 1
same_key_for_alldgs off off
sharedminorstart 33000 33000
storage_connectivity resilient resilient
usefssmartmove all all
DG VERSION:------------------------------------
root@pr01:>/#
vxdg list mdg
Group: mdg
dgid: 1478611264.33.pr01
import-id:
1024.12
flags:
version: 180 ç==========================
alignment:
8192 (bytes)
ssb: on
autotagging: on
detach-policy:
global
dg-fail-policy:
obsolete
ioship:
off
copies: nconfig=default nlog=default
config: seqno=0.1298 permlen=59071 free=59064
templen=5 loglen=8950
config
disk c1t2d0s2 copy 1 len=59071 state=clean online
config
disk c1t3d0s2 copy 1 len=59071 state=clean online
config
disk c1t4d0s2 copy 1 len=59071 state=clean online
config
disk c2t5d0s2 copy 1 len=59071 state=clean online
log disk
c1t2d0s2 copy 1 len=8950
log disk
c1t3d0s2 copy 1 len=8950
log disk
c1t4d0s2 copy 1 len=8950
log disk
c2t5d0s2 copy 1 len=8950
VERITAS PATHS: (SOLARIS):------------------------
PATH
VARIABLE --- /opt/VRTSvxfs/sbin
RELATED
DIR’s --- /usr/lib/fs/vxfs/bin
/etc/fs/vxfs
DEFAULT FS
FILE --- /etc/default/fs
TO GET THE
IDEA ABOUT HOW MUCH THROUGHPUT WE ARE GETTING FOR PARTICULAR DISK WITHINN DG :
---------
root@pr01:>/#
vxstat -g mdg -i3 -d
OPERATIONS BLOCKS AVG TIME(ms)
TYP
NAME READ WRITE
READ WRITE READ
WRITE
Thu Nov 10
12:24:48 2016
dm d3 16225 4706
100942 322634 0.17
0.82
dm d4 1 0
2048 0 65.67
0.00
dm d5 1173 4481
70738 325276 0.52
0.84
dm d6 0 0
0 0
0.00 0.00
Thu Nov 10
12:24:51 2016
dm d3 0 0 0 0
0.00 0.00
dm d4 0 0 0 0
0.00 0.00
dm d5 0 0 0 0
0.00 0.00
dm d6 0 0 0 0
0.00 0.00
Thu Nov 10
12:24:54 2016
dm d3 0 0 0 0
0.00 0.00
dm d4 0 0 0 0
0.00 0.00
dm d5 0 0 0 0
0.00 0.00
dm d6 0 0 0 0
0.00 0.00
Thu Nov 10
12:24:57 2016
dm d3 0 0 0 0
0.00 0.00
dm d4 0
0 0 0
0.00 0.00
dm d5 0 0 0 0
0.00 0.00
dm d6 0 0 0 0
0.00 0.00
^C
-g for dg
-I for
interval/iteration
-d for all
disks
VXTRACE:---------------------
Vxtrace
looks and captures every single i/o, by this we can analyze that how the
application is working and how the vxvm is handling those i/o’s.
Or what is
impact of those i/o’s on volume manager.
root@pr01:>/#
vxtrace -g mdg -d /tmp/output -o dev,disk mrvol |more
root@pr01:>/#
more /tmp/output
5fJ8mdgmrvol,c1t2d0s2$.!A
root@pr01:>/#
vxtrace -g mdg -f /tmp/output -o dev,disk mrvol |more
1 START
trim vdev mrvol block 16 len 2 concurrency 1 pid 3
2 START
trim disk c1t2d0s2 op 1 block 26 len 2
2 END
write disk c1t2d0s2 op 1 block 26 len 2 time 0
1 END
write vdev mrvol op 1 block 16 len 2 time 0
-d
/tmp/output redirecting
the o/p to particular file. Outpot would be in binary format.
-f
/tmp/output to convert
binary to ascii
root@pr01:>/#
vxtrace -g mdg -f /tmp/output >/tmp/output.txt
root@pr01:>/#
more /tmp/output.txt
1 START
trim vdev mrvol block 16 len 2 concurrency 1 pid 3
2 START
trim disk c1t2d0s2 op 1 block 26 len 2
2 END
write disk c1t2d0s2 op 1 block 26 len 2 time 0
1 END write
vdev mrvol op 1 block 16 len 2 time 0
root@pr01:>/#
vxtrace -g mdg -d /tmp/output -o dev,disk mrvol |more
ctrl+d
I did some
activities while running above cmd,
But the
o/p file is in binary, so we need to convert it in ascii by,
root@pr01:>/#
vxtrace -g mdg -f /tmp/output>/tmp/output.txt
root@pr01:>/#
more /tmp/output.txt
3 START
trim vdev mrvol block 16 len 2 concurrency 1 pid 3
4 START
trim disk c1t2d0s2 op 3 block 26 len 2
4 END
write disk c1t2d0s2 op 3 block 26 len 2 time 0
3 END
write vdev mrvol op 3 block 16 len 2 time 0
5 START
trim vdev mrvol block 72 len 2 concurrency 1 pid 7062
6 START
trim disk c1t2d0s2 op 5 block 82 len 2
6 END
write disk c1t2d0s2 op 5 block 82 len 2 time 0
5 END
write vdev mrvol op 5 block 72 len 2 time 0
7 START
trim vdev mrvol block 70681 len 2 concurrency 1 pid 0
8 START
trim disk c1t2d0s2 op 7 block 35363 len 2
8 END
write disk c1t2d0s2 op 7 block 35363 len 2 time 0
7 END
write vdev mrvol op 7 block 70681 len 2 time 1
9 START
trim vdev mrvol block 38446 len 2 concurrency 1 pid 3
10 START
trim disk c1t2d0s2 op 9 block 19256 len 2
11 START
trim vdev mrvol block 76 len 2 concurrency 2 pid 3
12 START
trim disk c1t2d0s2 op 11 block 86 len 2
10 END
write disk c1t2d0s2 op 9 block 19256 len 2 time 0
9 END
write vdev mrvol op 9 block 38446 len 2 time 0
12 END
write disk c1t2d0s2 op 11 block 86 len 2 time 0
11 END
write vdev mrvol op 11 block 76 len 2 time 0
13 START
trim vdev mrvol block 16 len 2 concurrency 1 pid 3
14 START
trim disk c1t2d0s2 op 13 block 26 len 2
14 END
write disk c1t2d0s2 op 13 block 26 len 2 time 0
13 END
write vdev mrvol op 13 block 16 len 2 time 0
15 START
trim vdev mrvol block 78 len 2 concurrency 1 pid 0
16 START
trim disk c1t2d0s2 op 15 block 88 len 2
16 END
write disk c1t2d0s2 op 15 block 88 len 2 time 1
15 END
write vdev mrvol op 15 block 78 len 2 time 1
17 START
trim vdev mrvol block 70683 len 3 concurrency 1 pid 0
18 START
trim disk c1t2d0s2 op 17 block 35365 len 3
18 END
write disk c1t2d0s2 op 17 block 35365 len 3 time 1
17 END
write vdev mrvol op 17 block 70683 len 3 time 1
19 START
trim vdev mrvol block 17968 len 128 concurrency 1 pid 7068
20 START
trim disk c1t2d0s2 op 19 block 9018 len 80
20 END
write disk c1t2d0s2 op 19 block 9018 len 80 time 0
21 START
trim disk c1t3d0s2 op 19 block 8970 len 48
21 END
write disk c1t3d0s2 op 19 block 8970 len 48 time 0
19 END
write vdev mrvol op 19 block 17968 len 128 time 0
22 START
trim vdev mrvol block 18096 len 128 concurrency 1 pid 7068
23 START
trim disk c1t3d0s2 op 22 block 9018 len 80
23 END
write disk c1t3d0s2 op 22 block 9018 len 80 time 0
24 START
trim disk c1t2d0s2 op 22 block 9098 len 48
24 END
write disk c1t2d0s2 op 22 block 9098 len 48 time 0
22 END
write vdev mrvol op 22 block 18096 len 128 time 0
========================O/P
REMOVED================================
root@pr01:>/#
VXTASK :--------------------------------------------
TASK = An
operation that is in progress on the system
TASK ID =
A unique no assigned to a single task
TASK TAG =
A string assigned to a task or tasks by the administrator to simplify task
management, we can specify a task
Tag using,
-t
<task_tag>
Vxtask cmd
to……..
=display
task info
=pause,
continue, and abort task
=modify
the progress rate of task
-l for
long listing
-h for
hierarchical printing with child task following the parent task.
root@pr01:>/#
vxtask -l list
root@pr01:>/#
vxtask -lh list
root@pr01:>/#
root@pr01:>/#
vxtask -ahlpr list
VXTASK MONITOR:---------------------------
vxtask [-c
count] [-ln] [-t time] [-w interval] monitor [task id/task tag]
-n shows info for tasks that are newly
registered while the prog is running
VXTASK ABORT|PAUSE|RESUME
#vxtask
pause 205
#vxtask
resume 205
#vxtask
abort 205
VXNOTIFY :-------------------------
root@pr01:>/#
vxnotify
connected
^C
root@pr01:>/#
vxnotify -f
connected
^C
Displays
info about all disks, plex and volume detachments as they occur
root@pr01:>/#
vxnotify -s -i
connected
^C
Displays
info about cluster config changes, including the import and deport of shared
DG.
root@pr01:>/#
VXVM CONFIGURATION DATABASE : ------------------
Config DB
stored in Private Region of disk
Live
replicated DB’s are referred as GOLDEN COPIES, we can keep upto 5 GOLDEN
COPIES.
If 2 disks
in DG both have GOLDEN COPIES, if 10 disks in DG only 5 have GOLDEN COPIES.
It
contains all disk, volume, plex and subdisk config records.
Updated by
“vxconfigd” process.
root@pr01:>/# vxdg list tdg
Group: tdg
dgid: 1478764230.18.pr01
import-id:
1024.17
flags:
version: 180
alignment:
8192 (bytes)
ssb: on
autotagging: on
detach-policy:
global
dg-fail-policy:
obsolete
ioship:
off
copies: nconfig=default nlog=default
config: seqno=0.1045 permlen=59071 free=59064
templen=3 loglen=8950
config
disk c1t2d0s2 copy 1 len=59071 state=clean online
config
disk c1t3d0s2 copy 1 len=59071 state=clean online
config
disk c1t4d0s2 copy 1 len=59071 state=clean online
config
disk c2t5d0s2 copy 1 len=59071 state=clean online
log disk
c1t2d0s2 copy 1 len=8950
log disk
c1t3d0s2 copy 1 len=8950
log disk
c1t4d0s2 copy 1 len=8950
log disk
c2t5d0s2 copy 1 len=8950
root@pr01:>/#
DISPLAYING HEADER INFO / DUMP PRIVATE REGION :
-----------------------
root@pr01:>/#
vxdg list c1t2d0s2
VxVM vxdg
ERROR V-5-1-582 Disk group c1t2d0s2: No such disk group
root@pr01:>/#
vxdisk list c1t2d0s2
Device: c1t2d0s2
devicetag:
c1t2d0
type: auto
hostid: pr01
disk: name=d2 id=1478609673.26.pr01
group: name=tdg id=1478764230.18.pr01
info:
format=sliced,privoffset=4,pubslice=4,privslice=3
flags: online ready private autoconfig autoimport
imported
pubpaths: block=/dev/vx/dmp/c1t2d0s4
char=/dev/vx/rdmp/c1t2d0s4
privpaths:
block=/dev/vx/dmp/c1t2d0s3 char=/dev/vx/rdmp/c1t2d0s3
guid: -
udid:
VMware%2C%5FVMware%20Virtual%20S%5FDISKS%5F6000C29CDBCEC6B58E9B0680229EC0AD
site: -
version: 2.1
iosize: min=512 (bytes) max=2048 (blocks)
public: slice=4 offset=0 len=20836305
disk_offset=96390
private: slice=3 offset=4 len=80065 disk_offset=16065
update: time=1478764240 seqno=0.26
ssb: actual_seqno=0.0
headers: 0 248
configs: count=1 len=59071
logs: count=1 len=8950
Defined
regions:
config
priv 000017-000247[000231]: copy=01 offset=000000 enabled
config
priv 000249-059088[058840]: copy=01 offset=000231 enabled
log
priv 059089-068038[008950]: copy=01 offset=000000 enabled
Multipathing
information:
numpaths: 1
c1t2d0s2 state=enabled
root@pr01:>/#
VXVM DAEMONS : ------------------------------------
Vxconfigd
: -
Ø
maintains system configuration in the kernel
and disk (private region). If the daemon is stopped it does not disable any
config state loaded in kernel,
vxconfigd:
Ø
Maintains the configuration database
Ø
Synchronizes changes between multiple
requests, based on a database transaction model.
Ø
vxconfigd reads the kernel log to determine current
states of VxVM components and updates the configuration database
Ø
Kernel logs are updated even if vxconfigd is
not running. For Example, upon start-up, vxconfigd reads the kernel logs and
determines that a volume needs to be resynchronized.
It can be
in three states:
Enable= Normal
mode
Disable
=
Most operations cannot be be used
Booted
=
Normal startup while using boot disk group
vxrelocd
Ø
Monitors for failure events and relocates
failed subdisks
vxconfigbackupd
Ø
Used to backup configuration changes, the files
created can be used with vxmake to restored lost groups.
vxnotify
Ø
Display Veritas volume manager events used
with the vxconfigd daemon
vxiod:
Ø
vxvm I/O kernel threads provides extended I/O
operations without blocking calling processes. By default 16 I/O threads are
started at boot time, and at least 1 I/O thread must be run all the times.
The vxdctl Command
Vxdctl
manages
the states of volume configuration daemon “vxconfigd”
Use vxdctl
to control vxconfigd.
# vxdctl mode Display
vxconfigd status
# vxdctl mode
mode: enabled
# vxdctl enable Enables
vxconfigd
#
vxdctl disable
Disabled vxconfigd
#
vxdctl stop To
Stop the vxconfigd daemon
# vxconfigd To start
vxconfigd
#
vxdctl license display vxdctl
license
# vxrelocd Daemon
Ø
vxrelocd is the hot
relocation daemon that monitors events that effect redundancy. Data affected
from mirrored or RAID-5 subdisk are relocated to spare disks or other free
space within the disk group.
Ø
vxrelocd notifies
the system administrator by email of redundancy failures and relocation
activities.
# vxiod Daemon
Ø
Volume extended I/O daemon that allows for
extended I/O operation without blocking calling processes.
# vxnotify Daemon
Ø
Notifies of events relating to disk and
configuration changes
# vxconfigbackupd (Veritas)
VXVM LOG : -------------------------------------------
VERITAS
Volume Manager (tm) provides the option of logging console output to a file.
The Volume Manager configuration daemon vxconfigd controls whether such logging
is turned on or off, which by default, is disabled. If enabled, the default log
file is vxconfigd.log, and its location varies by operating system:
Operating
System Log File
AIX
/var/adm/ras/vxconfigd.log
HP-UX /var/adm/vxconfigd.log
Linux /etc/vx/vxconfigd.log
Solaris /var/vxvm/vxconfigd.log
vxconfigd
Ø
also supports the use of syslog to log all of
its regular console messages. When this is enabled, all console output is
directed through the syslog interface.
Ø
To enable logging of console output to a file,
either invoke vxconfigd as follows or edit the Volume Manager startup script
(described later):
# vxconfigd [-x [1-9]] -x log
The option
-x [1-9] is required to get any debug output. So, if -x 9 -x log is mentioned,
then messages will get logged to /var/vxvm/vxconfigd.log.
To enable
syslog logging of console output, either invoke vxconfigd as follows or edit
the Volume Manager startup script (described later):
#
vxconfigd -x syslog
When -x
syslog is used, debug messages are not logged. Only error, fatal error,
warning, and notice messages are logged.
If -x 9 -x log -x syslog is specified,
then all the debug messages only go to vxconfigd.log, but error messages
go to both vxconfigd.log and to the log file specified in syslog.conf. Refer to
the syslog and syslog.conf man pages for more information.
An
alternate method of enabling log file and/or syslog logging is to edit the
Volume Manager startup script:
Operating
System Startup Script
AIX
/etc/init.d/vxvm-sysboot
HP-UX
/sbin/init.d/vxvm-sysboot
Linux /etc/vx/vxvm-startup
Solaris /etc/init.d/vxvm-sysboot
Modify the
following portion of the Volume Manager startup script this way:
1. Uncomment any of the following lines to
enable the corresponding option in vxconfigd:
#opts="$opts
-x syslog" # use
syslog for console messages
#opts="$opts
-x log" #
messages to /var/vxvm/vxconfigd.log
#opts="$opts
-x logfile=/foo/bar" # specify
an alternate log file
#opts="$opts
-x timestamp" #
timestamp console messages
2. Uncomment the following line:
#debug=1 # enable
debugging console output
It is
necessary to uncomment the line regarding "debug". The higher the debug level (0-9), the greater
the output.
VXVM DEBUG : -----------------------------------------
root@pr01:>/#
vxconfigd -k -m enable -x syslog (log to syslog)
root@pr01:>/#
vxconfigd -k -m enable -x log (log
to /var/vxvm/vxconfigd.log)
root@pr01:>/#
vxconfigd -k -m enable -x logfile=/tmp/vxconfiglog.txt
root@pr01:>/#
more /tmp/vxconfiglog.txt
11/12
11:09:38: VxVM vxconfigd NOTICE V-5-1-16765 Selecting configuration database
copy from c1t3d0s2 from disks: c1t3d0
s2
c1t4d0s2 c1t2d0s2 c2t5d0s2
11/12
11:09:39: VxVM vxconfigd NOTICE V-5-1-16766 Trying to import the disk group
tdg using configuration database copy
from
c1t3d0s2
IMPORTANT FILES :
---------------------------------------------------
root@pr01:>/#
more /etc/vx/volboot
volboot
3.1 0.1 120
hostid
pr01
hostguid
{92450c9c-a0fb-11e6-9c83-000c299e7c6a}
request_threads
2
Command_Shipping
1
end
IF
HOSTNAME CHANGED, ALWAYS CHANGE THE HOSTID……….
#vxdctl
hostid <new hostname>
#vxdctl
enable
TO RECREATE VOLBOOT :--------------------------
#vxdctl
init <hostname>
DG BACKUP:
-----------------------------------------------------------------------
root@pr01:>/#
ls -l /etc/vx/cbr/bk
total 18
drwxr-xr-x 4 root
root 512 Nov 11 10:40
mdg.1478611264.33.pr01
drwxr-xr-x 2 root
root 512 Nov 3 19:21 new-dg3.1478178976.38.pr01
drwxr-xr-x 2 root
root 512 Nov 4 18:23 newdg.1478262364.54.pr01
drwxr-xr-x 3 root
root 512 Nov 6 02:40 tdg.1478371412.17.pr01
drwxr-xr-x 2 root
root 512 Nov 6 03:55 tdg.1478384145.25.pr01
drwxr-xr-x 4 root
root 512 Nov 7 18:55 tdg.1478404383.16.pr01
drwxr-xr-x 2 root
root 512 Nov 12 09:44
tdg.1478764230.18.pr01
drwxr-xr-x 2 root
root 512 Nov 3 19:20 test-dg.1478178077.32.pr01
drwxr-xr-x 2 root
root 512 Nov 3 19:22 test-dg2.1478178949.36.pr01
root@pr01:>/#
ALL COMMANDS LOG:
--------------------------------------------------------------
root@pr01:>/#
tail -20 /var/adm/vx/cmdlog
# 0,
15046, Sat Nov 12 11:07:19 2016
/usr/sbin/vxconfigd
-k -m enable -x syslog
# 16128,
15074, Sat Nov 12 11:07:27 2016
/usr/sbin/vxdisk
-q list
# 13838,
15075, Sat Nov 12 11:07:27 2016
/sbin/vxdmpadm
getdmpnode all
# 24006,
15077, Sat Nov 12 11:07:27 2016
/usr/sbin/vxdg
-q list
# 8627,
15078, Sat Nov 12 11:07:27 2016
/usr/sbin/vxprint
-g tdg -F%name:%assoc:%last_diskid:%udid: -d
# 0,
15104, Sat Nov 12 11:09:37 2016
/usr/sbin/vxconfigd
-k -m enable -x logfile=/tmp/vxconfiglog.txt
# 13140,
15132, Sat Nov 12 11:09:43 2016
/usr/sbin/vxdisk
-q list
# 9196,
15133, Sat Nov 12 11:09:43 2016
/sbin/vxdmpadm
getdmpnode all
# 23198,
15135, Sat Nov 12 11:09:43 2016
/usr/sbin/vxdg
-q list
# 10437,
15136, Sat Nov 12 11:09:43 2016
/usr/sbin/vxprint
-g tdg -F%name:%assoc:%last_diskid:%udid: -d
VOLD
LOG:---------------------------------------------------
root@pr01:>/#
tail -20 /var/adm/vold.log
IMPORTED DG INFO:----------------------------------------------------
root@pr01:>/#
ls -l /var/vxvm/tempdb/
total 32
-rw-r--r-- 1 root
root 2048 Nov 11 10:24 mdg
-rw-r--r-- 1 root
root 1536 Nov 6 08:54 mydg
-rw-r--r-- 1 root
root 1536 Nov 3 19:37 new-dg3
-rw-r--r-- 1 root
root 3072 Nov 4 19:29 newdg
-rw-r--r-- 1 root
root 1536 Nov 11 10:19 tdg
-rw-r--r-- 1 root
root 1024 Nov 3 18:47 test-dg
-rw-r--r-- 1 root
root 1024 Nov 3 18:47 test-dg2
-rw-r--r-- 1 root
root 1024 Nov 3 19:01 test-dg3
-rw-r--r-- 1 root
root 1536 Nov 5 12:22 testdg
VXVM LOGGING: ------------------------------
root@pr01:>/#
cp /lib/svc/method/vxvm-sysboot /lib/svc/method/vxvm-sysboot.bkp
root@pr01:>/#
vi /lib/svc/method/vxvm-sysboot
Uncomment
Following,
opts="$opts
-x syslog" # use
syslog for console messages
opts="$opts
-x log" #
messages to /var/vxvm/vxconfigd.log
opts="$opts
-x timestamp" # timestamp console messages
debug=9 # enable debugging
console output
Then
reboot the system or,
root@pr01:>/#
vxdctl stop
root@pr01:>/#
vxconfigd –k
To enable
Temporary logging to console,
root@pr01:>/#
vxconfigd -x [1-9] -x log
11/12
18:31:59: VxVM vxconfigd DEBUG
V-5-1-24577
VOLD
STARTUP pid=15346 debug-level=1 logfile=/var/vxvm/vxconfigd.log
^C
root@pr01:>/#
more /var/vxvm/vxconfigd.log
11/12
11:05:00: VxVM vxconfigd NOTICE V-5-1-16765 Selecting configuration data
base copy
from c1t3d0s2 from disks: c1t3d0s2 c1t2d0s2 c1t4d0s2 c2t5d0s2
11/12
11:05:01: VxVM vxconfigd NOTICE V-5-1-16766 Trying to import the disk gr
oup tdg
using configuration database copy from c1t3d0s2
To enable
syslog logging of console,
root@pr01:>/#
vxconfigd -x syslog
With only
–x syslog, it will only record error, fatal error, warning and notices
If,
root@pr01:>/#
vxconfigd -x 9 -x log -x syslog
11/12
18:43:33: VxVM vxconfigd DEBUG
V-5-1-24577
VOLD
STARTUP pid=15416 debug-level=9 logfile=/var/vxvm/vxconfigd.log
root@pr01:>/#
then all
debug messages go to logfile=/var/vxvm/vxconfigd.log but error messages go to
both vxconfigd.log as well as syslog
TROUBLESHOOTING FILES / TOOLS :
--------------------------------------------
Ø
/var/vxvm/vxconfigd.log
Ø
/var/log/syslog
Ø
/var/adm/messages
DEBUGGING TOOLS ARE LOCATED AT,
root@pr01:>/#
cd /opt/VRTSspt/
root@pr01:>/opt/VRTSspt#
ls -ltr
total 12
-rwxr-xr-x 1 root
other 1700 Jan 17 2012 README.VRTSspt
drwxr-xr-x 6 root
other 512 Nov 2 17:56 FS
drwxr-xr-x 2 root
other 512 Nov 2 17:56 DataCollector
drwxr-xr-x 2 root
other 1024 Nov 2 17:56 FirstLook
drwxr-xr-x 2 root
other 512 Nov 2 17:56 VRTSexplorer
EX:---
root@pr01:>/opt/VRTSspt#
cd FS
root@pr01:>/opt/VRTSspt/FS#
ls -ltr
total 8
drwxr-xr-x 2 root
other 512 Nov 2 17:56 Cfstlist
drwxr-xr-x 2 root
other 512 Nov 2 17:56 FsCompactIList
drwxr-xr-x 2 root
other 512 Nov 2 17:56 MetaSave
drwxr-xr-x 2 root
other 512 Nov 2 17:56 VxBench
root@pr01:>/opt/VRTSspt/FS#
cd VxBench
root@pr01:>/opt/VRTSspt/FS/VxBench#
ls -ltr
total 1106
-rwxr-xr-x 1 root
other 508 Dec 5 2006
README.vxbench
-rwxr-xr-x 1 root
other 310160 Jul 28 2011 vxbench_10
-rwxr-xr-x 1 root
other 237248 Jun 27 2012 vxbench_11
root@pr01:>/opt/VRTSspt/FS/VxBench#
more README.vxbench
vxbench is
a tool available on AIX, HP-UX, Linux, Solaris Sparc and
Opteron
for benchmarking I/O loads on raw disk or file systems. It
can
generate various I/O workloads such as sequential and random
reads/writes,
asynchronous I/Os, and memory mapped (mmap) operations.
It also
has many options specific to the Veritas File System (VxFS).
For a list
of the options, run:
./vxbench_<os> -h
For
Solaris 10, use vxbench_10.
Special
Note: For ga5_0_maint Opteron, we only
support Solaris 10 update 2.
root@pr01:>/opt/VRTSspt/FS/VxBench#
./vxbench_10
./vxbench_10:
must specify a workload
usage:
./vxbench_10 -w workload [options] filename ...
Valid
options are:
-h
print more detailed help message
-P
use procs for users, threads for multihreaded I/O (default)
-p
use processes for users and for multithreaded I/O
-t
use threads for users and for multithreaded I/O
-l
lock I/O buffers in memory
-s
for multiuser tests only print summary results
-v
for multithreaded tests print per-thread results
-k
print throughput in kbytes/sec (default)
-m
print throughput in mbytes/sec
-w workload select a type of I/O workload
valid workloads are:
read sequential read of the test files
write sequential write of the test files
rand_read random read of the test files
rand_write random write of the test files
rand_mixed mix of random reads and writes
mmap_read use mmap to read the test files
mmap_write use mmap to overwrite the test files
aread sequential aioread of the test files
awrite sequential aiowrite of the test files
arand_mixed mix of random aioreads and aiowrites
-i subopts specify suboptions describing test
-o opentype specify flags for opening the file
-c cacheopts specify vxfs caching advisories
-e extsize specify a fixed extent size
-r reservation specify space reservation
-f flags specify flags for reservation and fixed
extents
root@pr01:>/opt/VRTSspt/FS/VxBench#
EXPLORER :
------------------------------------------------------
/opt/VRTSspt/VRTSexplorer
root@pr01:>/opt/VRTSspt#
cd VRTSexplorer
root@pr01:>/opt/VRTSspt/VRTSexplorer#
ls -ltr
total 24
-rwxr-xr-x 1 root
other 8381 Jul 18 2012 VRTSexplorer
-rwxr-xr-x 1 root
other 2343 Jul 18 2012 README.vxexplorer
root@pr01:>/opt/VRTSspt/VRTSexplorer#
./VRTSexplorer
==========================………….==========================
Press
[Enter] to continue
Redirect
command:
/opt/VRTSspt/DataCollector/sort/sortdc
-vxexplorer pr01
For
additional details, see the technote:
Using SORT Data Collector (formerly VOS)
to gather and submit
a vxexplorer troubleshooting archive
http://www.symantec.com/docs/HOWTO32575
More
information about the Data Collector may also be found
in the
file:
/opt/VRTSspt/DataCollector/README.data_collector
file
Press
[Enter] to continue
SORT Data
Collector has not been initialized.
======================O/P
REMOVED===========================================
ftp.veritas.com/incoming?
[y,n,q] (y) n
Please ftp
the output file(s) to SORT ftp site: ftp.veritas.com/incoming.
SORT data
collector current session log files are saved at:
/opt/VRTSspt/DataCollector/sort/log/sortdc-201611121854iBe
root@pr01:>/opt/VRTSspt/VRTSexplorer#
SYSTEM LEVEL DEBUGGING TOOLS :
---------------------------------
adb (to exit $q)
kadb
crash
root@pr01:>/#
man adb
Reformatting
page. Please Wait... done
User
Commands
adb(1)
NAME
adb - general-purpose debugger
SYNOPSIS
adb [-kw] [-I dir] [-P prompt] [-V mode] [
object [ core]]
DESCRIPTION
The adb utility is an interactive,
general-purpose debugger.
It
can be used to examine files and provides a
controlled
environment for the execution of programs.
The adb utility is now implemented as a
link to the mdb(1)
utility. mdb(1) is a low-level debugging
utility that can be
used to examine user processes as well as
the live operating
system or operating system crash dumps.
The new mdb(1) util-
ity
provides complete backwards
compatibility with the
existing
syntax and features of adb,
including support for
processing adb macro files. The
Solaris Modular Debugger
Guide
and mdb(1) man
page describes the features of mdb,
including its adb compatibility mode.
This mode will
be
activated by default when the adb link is
executed.
Introduction to volume manager
Volume
manager is software which is used to following purpose:-
* Increase
the storage capacity online
*Increase
the data availability online
*Increase
the performance online
Advantages of Veritas Volume Manager
* Its
Supports hydrogenous environment
* Its
supports peta bytes
* 4000 sub
disks per 1 vmdisk
* Man page
size of the volume can be up to 255tb
* Online
file system management
* Fast
file system recovery
*Fast file
system Reboot
No comments:
Post a Comment