Difference between /usr/sbin/ps & /usr/ucb/ps command
The command that is equivalent to /usr/usb/ps -axu is "ps -aef"
/usr/ucb/ps is BSD
/usr/sbin/ps is SVR4
/usr/ucb/ps -www ==as wide as possible, this over comes the 80 column restriction that is seen in normal ps -ef command.
To see which executable is being run by a process, '/usr/ucb/ps auxwww' can be used. it shows you the exact command that invoked all the processes you see via 'ps'.
Tuesday, March 26, 2013
Wednesday, February 20, 2013
modinfo
solaris1:/root# modinfo
Id Loadaddr Size Info Rev Module Name
0 1000000 1f0bb8 - 0 unix ()
1 10af380 23c6b0 - 0 genunix ()
2 1294a90 1620 - 0 platmod ()
3 1295f00 d5c8 - 0 FJSV,SPARC64-VII ()
5 129e000 4be8 1 1 specfs (filesystem for specfs)
6 12a29e8 38a8 3 1 fifofs (filesystem for fifo)
7 7afa0000 18750 218 1 dtrace (Dynamic Tracing)
8 12a60c8 4248 16 1 devfs (devices filesystem 1.16)
9 12a9f78 1c0a8 5 1 procfs (filesystem for proc)
12 12c7248 39f8 1 1 TS (time sharing sched class)
13 12ca460 8dc - 1 TS_DPTBL (Time sharing dispatch table)
14 12ca4f0 384a0 2 1 ufs (filesystem for ufs)
15 1300138 21c - 1 fssnap_if (File System Snapshot Interface)
16 13002b0 1d28 1 1 rootnex (sun4 root nexus 1.15)
17 1301b20 1bc 57 1 options (options driver)
..............
solaris1:/root# modinfo -c
Id Loadcnt Module Name State
0 1 unix LOADED/INSTALLED
1 1 genunix LOADED/INSTALLED
2 1 platmod LOADED/INSTALLED
3 1 FJSV,SPARC64-VII LOADED/INSTALLED
4 0 cl_bootstrap UNLOADED/UNINSTALLED
5 1 specfs LOADED/INSTALLED
6 1 fifofs LOADED/INSTALLED
7 1 dtrace LOADED/INSTALLED
8 1 devfs LOADED/INSTALLED
9 1 procfs LOADED/INSTALLED
10 1 swapgeneric UNLOADED/UNINSTALLED
11 0 lbl_edition UNLOADED/UNINSTALLED
12 1 TS LOADED/INSTALLED
..............
modload - load a kernel module (filename)
modunload - unload a module (using module_id)
Sunday, February 10, 2013
Solaris x86 - Console GUI and CLI
On Solaris x86 servers, Console can be launched from both GUI and the CLI.
start /SP/console
or
Web GUI -> Remote Control -> Launch Remote Console
Both the consoles can show the POSt and grub load process.
But once the OS is loaded after the OS selection screen, one of the screen can go Black based on the eeprom setting.
eg)
MySolaris:/root# prtdiag -v | head -1
System Configuration: Sun Microsystems SUN FIRE X4250
MySolaris:/root#
MySolaris:/root# eeprom | grep console
console=text
MySolaris:/root#
If console = 'ttya' then the serial console (/SP/console) will be active
If console = 'text' then the VGA port (i.e., the redirected remote console) will be active.
If you change the eeprom console setting, an O/S reboot will be needed.
Tuesday, January 29, 2013
Resetting SC from the machine - v490
Sun-Fire-V490's rsc can be reset from the machine
(MySolaris:/root)# cd /usr/platform/`uname -i`/
(MySolaris:/usr/platform/SUNW,Sun-Fire-V490)#
(MySolaris:/usr/platform/SUNW,Sun-Fire-V490)# cd rsc/
(MySolaris:/usr/platform/SUNW,Sun-Fire-V490/rsc)#
(MySolaris:/usr/platform/SUNW,Sun-Fire-V490/rsc)# ls
rsc-config rsc-initscript rscadm
(MySolaris:/usr/platform/SUNW,Sun-Fire-V490/rsc)#
(MySolaris:/usr/platform/SUNW,Sun-Fire-V490/rsc)# ./rscadm resetrsc
Are you sure you want to reboot RSC (y/n)? y
(MySolaris:/usr/platform/SUNW,Sun-Fire-V490/rsc)#
(MySolaris:/usr/platform/SUNW,Sun-Fire-V490/rsc)# uname -a
SunOS MySolaris 5.10 Generic_147440-11 sun4u sparc SUNW,Sun-Fire-V490
(MySolaris:/usr/platform/SUNW,Sun-Fire-V490/rsc)#
Sunday, January 27, 2013
Login delays
su - < nis user> is taking a long time ( more than 20 sec )
Some introduction to the problem:
When is the slowness observed su only or even with telnet and ssh?
Answer: Even telnet and ssh is slow. Basically “su -
When slowness is observed,is it just before you get logged in or even after that with commands?
Answer: Only the login is very slow. Once login everything looks normal.
(MySolaris:/)# time su - schweitz -c "hostname"
Sun Microsystems Inc. SunOS 5.10 Generic January 2005
#############################################################
# This server is using NIS
#############################################################
MySolaris
real 0m20.180s
user 0m0.040s
sys 0m0.070s
(MySolaris:/)#
First test:
Difference in time between "su schweitz" and "su - schweitz".
With "su - username" the HOME directory has to be mounted and the shell profiles (system and user specific) get executed. (sh,ksh: /etc/profile, $HOME/.profile; for C-shell ist equivalent). May be those profiles contain command wich run slow (like 'quota').
(MySolaris:/)# time su - schweitz -c "hostname"
su is working fine. su - is taking long time
Second Test:
All users have csh as its shell
rename /etc/.login (used by csh") :
# mv /etc/.login /etc/.login.not
Then test "su - xxx" :
# time su - schweitz -c "hostname"
after moving the /etc/.login, it is indeed fast
(MySolaris:/)# time su - schweitz -c "hostname"
MySolaris
real 0m0.055s
user 0m0.016s
sys 0m0.027s
(MySolaris:/)#
The real problem:
In the resultant truss output, it was noted that quota command takes more than 20 sec.
So issue seems to be with quota command. The "quota" command also checks NFS mounted file systems. One of the NFS servers seems not to respond. So removed an NFS mount and then the su was fast.
The 20 sec delay is caused by checking quotas on NFS mounted file systems; it occurs when some NFS server does not respond.
Thursday, January 17, 2013
Clearing a minor fmadm faulty alert
(MySolaris:/)# fmadm faulty
--------------- ------------------------------------ -------------- ---------
TIME EVENT-ID MSG-ID SEVERITY
--------------- ------------------------------------ -------------- ---------
Dec 16 22:36:07 96c775c2-6764-6eae-ea5b-ea57f62cc2c0 FMD-8000-0W Minor
Host : MySolaris
Platform : SUNW,Sun-SPARC Enterprise T5240 Chassis_id :
Product_sn :
Fault class : defect.sunos.fmd.nosub
FRU : None
faulty
Description : The Solaris Fault Manager received an event from a component to
which no automated diagnosis software is currently subscribed.
Refer to http://sun.com/msg/FMD-8000-0W for more information.
Response : Error reports from the component will be logged for examination
by Sun.
Impact : Automated diagnosis and response for these events will not occur.
Action : Run pkgchk -n SUNWfmd to ensure that fault management software is
installed properly. Contact Sun for support.
(MySolaris:/)#
The FMADM fault currently logged on this system is caused by a logical inconsistency in the checkpointed data, causing the system do disable cpumem-diagnosis. As described in the attached document, this in turn, causes the FMD-8000-0W defect.sunos.fmd.nosub on the next transient memory error which should have been handled by the cpumem-diagnosis module. We can clear the FMD-8000-0W, but any little thing which cpumem-diagnosis would normally handle will trigger another FMD-8000-0W defect.sunos.fmd.nosub. Please see belowtThe resolution for this issue:
First roll the logs and restart the FMA daemon to keep the history.
logadm -p now -s 1b /var/fm/fmd/errlog
logadm -p now -s 1b /var/fm/fmd/fltlog
svcadm restart fmd
...wait two minutes...
Now scrub the checkpoint files
svcadm disable -st fmd
find /var/fm/fmd/ckpt -type f | xargs rm
svcadm enable fmd
...wait 2 minutes...
Now see if everything is clear
fmadm config - check that cpumem-diagnosis is active
fmadm faulty -a - shouldn't return anything
also check to see if we logged any new errors on fmd startup; if we did, we'll need to check further...
fmdump -e
should return nothing
Monday, October 22, 2012
NFS share issues with multiple ip on a host
NAS box has a share which is to be mounted on a client
NAS box: myNasBox
Client: SolZone1
NAS box has provided access to the ip/hostname of the host
(SolZone1:/)# nslookup SolZone1
Server: 10.10.134.3
Address: 10.10.134.3#53
Name: SolZone1.bc
Address: 45.26.20.216
But the mounting failed with permission error
(SolZone1:/)# mount -F nfs -o rw,bg,soft,vers=3 myNasBox:/nasdump/nasdata /nasdata
nfs mount: myNasBox:/nasdump/nasdata: Permission denied
Issue identified as below
(SolZone1:/)# traceroute myNasBox
traceroute: Warning: Multiple interfaces found; using 10.12.12.12 @ aggr535001:3
traceroute to myNasBox (10.12.11.45), 30 hops max, 40 byte packets
1 10.13.142.2 (10.13.142.2) 0.713 ms 0.710 ms 0.574 ms
2 172.27.128.113 (172.27.128.113) 3.354 ms 3.056 ms 2.407 ms
3 172.27.128.142 (172.27.128.142) 2.375 ms 8.416 ms 2.308 ms
4 nas-box-14 (10.12.11.45) 1.406 ms 1.481 ms 1.427 ms
(SolZone1:/)#
The traffic comes through the ip 10.12.12.12
(SolZone1:/)# nslookup 10.12.12.12
Server: 10.10.134.3
Address: 10.10.134.3#53
12.142.120.10.in-addr.arpa name = SolZone1-lb.bc.
Multiple ip's for the host
(SolZone1:/)# ifconfig -a
lo0:7: flags=2001000849
inet 127.0.0.1 netmask ff000000
aggr209001:1: flags=201000843
inet 45.16.20.26 netmask fffffe00 broadcast 45.216.205.255
aggr302001:3: flags=201000843
inet 45.29.1.8 netmask ffffff00 broadcast 45.219.1.255
aggr535001:3: flags=201000843
inet 10.12.12.12 netmask ffffff00 broadcast 10.13.142.255
nxge200006:1: flags=201000843
inet 10.28.18.165 netmask fffffe00 broadcast 10.48.129.255
(SolZone1:/)#
NAS is adapted to permit the ip 10.12.12.12.
Now the mount is successfull
(SolZone1:/)# mount -F nfs -o rw,bg,soft,vers=3 myNasBox:/nasdump/nasdata /nasdata
(SolZone1:/)# bdf /nasdata
Filesystem kbytes used avail capacity Mounted on
myNasBox:/nasdump/nasdata
4017992400 1317611268 2722172800 33% /nasdata
(SolZone1:/)#
"kill -9" fails... why?
Kill -9 >> Process still alive !!!!
A signal is a message sent to a process to interrupt it and cause a response. If the process has been designed to respond to signals of the type sent it does so; otherwise, it terminates. There are 42 signals, as defined in the signal(5) man page.
Why sometime process cannot be killed with kill -9?
If the process is hung waiting for I/O (or some other kernel resource) it will behave that way. The problem is the process is hung waiting for an I/O to return and is unable to service the signal. So it never gets killed. Usually reboot is the only solution for this condition.
Sometimes a process will be waiting for kernel to do some I/O and the kernel is waiting for a timeout because of a hardware error, etc. This can happen if you try to do a file copy for instance and a harddrive fails. The 'cp' command may not be killable until the kernel timeout has occurred (this may hang indefinately).
stale NFS mounts will cause the issue if hard mount is used. One way to avoid hung processes is to "soft" mount the NFS mounts.
https://forums.oracle.com/thread/2398407
http://docs.oracle.com/cd/E19455-01/806-1360/processmanagerusing-62/index.html
Monday, October 15, 2012
HP-UX sw* operations
HP-UX Package install/uninstall/list operations
### Find the available depot on a host
in the local host :
**swlist -i -d @ /var/opt/pkgs/depots/Rel.11.31/apps
In a remote host :
root@MyHPHOST:/hroot# swlist -l depot -s MyHPHOST2 -d /var/opt/pkgs/depots/Rel.11.31/apps
# Initializing...
# Target "MyHPHOST2" has the following depot(s):
/var/opt/pkgs/depots/Rel.11.23/core
/var/opt/pkgs/depots/Rel.11.23/apps
/var/opt/pkgs/depots/Rel.11.31/core
/var/opt/pkgs/depots/Rel.11.31/apps
/var/opt/pkgs/depots/Rel.11.11/core
/var/opt/pkgs/depots/Rel.11.11/apps
/var/spool/sw
root@MyHPHOST:/hroot#
### Find a specific Package in the depot
root@MyHPHOST:/hroot# swlist -d -l product NMSAP @ MyHPHOST2:/var/opt/pkgs/depots/Rel.11.31/apps
# Initializing...
# Contacting target "MyHPHOST2"...
#
# Target: MyHPHOST2:/var/opt/pkgs/depots/Rel.11.31/apps
#
NMSAP 4.0 NetWorker Module for SAP with Oracle
root@MyHPHOST:/hroot#
root@MyHPHOST:/hroot# swlist -d -l product @ MyHPHOST2:/var/opt/pkgs/depots/Rel.11.31/apps | grep NMSAP
NMSAP 4.0 NetWorker Module for SAP with Oracle
root@MyHPHOST:/hroot#
### Find the list of files in a specific package
root@MyHPHOST:/hroot# swlist -d -l file NMSAP @ MyHPHOST2:/var/opt/pkgs/depots/Rel.11.31/apps
# Initializing...
# Contacting target "MyHPHOST2"...
#
# Target: MyHPHOST2:/var/opt/pkgs/depots/Rel.11.31/apps
#
# NMSAP 4.0 NetWorker Module for SAP with Oracle
# NMSAP.lgto-nmsap 4.0 NetWorker Module for SAP with Oracle
/etc/init.utl
/etc/nsrsapsv.cfg
/etc/nwsldreg.xml
/opt/networker/bin/backint
/opt/networker/bin/nsrsapadm
/opt/networker/bin/nsrsapprobe
/opt/networker/bin/nsrsapra
/opt/networker/bin/nsrsaprachild
/opt/networker/bin/nsrsapsv
/opt/networker/bin/sapclone
/opt/networker/bin/sapra.jar
/opt/networker/bin/sapra_res.jar
/opt/networker/lib/apps/nmsap/hpux64/libcommonssl.7.6.dev.139.so
/opt/networker/man/man8/backint.8
/opt/networker/man/man8/nsrsapadm.8
/opt/networker/man/man8/nsrsapprobe.8
/opt/networker/man/man8/nsrsapsv.8
/opt/networker/man/man8/sapclone.8
/usr/lib/libnworasap.so
root@MyHPHOST:/hroot#
### Remove a package
root@MyHPHOST:/hroot# swlist -l product | grep NMSAP
NMSAP 3.5 EMC NetWorker Module for SAP with Oracle
root@MyHPHOST:/hroot#
root@MyHPHOST:/hroot# swremove NMSAP
======= 08/21/13 14:26:51 METDST BEGIN swremove SESSION
(non-interactive) (jobid=MyHPHOST-0432)
* Session started for user "root@MyHPHOST".
* Beginning Selection
* Target connection succeeded for "MyHPHOST:/".
* Software selections:
NMSAP.lgto-nmsap,l=/,r=3.5,a=HP-UX_11.XX_64
* Selection succeeded.
* Beginning Analysis
* Session selections have been saved in the file
"/hroot/.sw/sessions/swremove.last".
* The analysis phase succeeded for "MyHPHOST:/".
* Analysis succeeded.
* Beginning Execution
* The execution phase succeeded for "MyHPHOST:/".
* Execution succeeded.
NOTE: More information may be found in the agent logfile using the
command "swjob -a log MyHPHOST-0432 @ MyHPHOST:/".
======= 08/21/13 14:27:11 METDST END swremove SESSION
(non-interactive) (jobid=MyHPHOST-0432)
root@MyHPHOST:/hroot# swlist -l product | grep NMSAP
root@MyHPHOST:/hroot#
### Install a package
root@MyHPHOST:/hroot# swinstall -s MyHPHOST2:/var/opt/pkgs/depots/Rel.11.31/apps NMSAP
======= 08/21/13 14:30:47 METDST BEGIN swinstall SESSION
(non-interactive) (jobid=MyHPHOST-0433)
* Session started for user "root@MyHPHOST".
* Beginning Selection
* Target connection succeeded for "MyHPHOST:/".
* Source connection succeeded for
"MyHPHOST2:/var/opt/pkgs/depots/Rel.11.31/apps".
* Source:
MyHPHOST2:/var/opt/pkgs/depots/Rel.11.31/apps
* Targets: MyHPHOST:/
* Software selections:
NMSAP.lgto-nmsap,r=4.0,a=HP-UX_11.XX_64
+ NetWorker.nwr-cbin,r=7.6.3,a=HP-UX_11.XX_64
* A "+" indicates an automatic selection due to dependency or
the automatic selection of a patch or reference bundle.
* Selection succeeded.
* Beginning Analysis and Execution
* Session selections have been saved in the file
"/hroot/.sw/sessions/swinstall.last".
* "MyHPHOST:/": 1 filesets have a version with a higher
revision number already installed.
ERROR: "MyHPHOST:/": The software dependencies for 1 products or
filesets cannot be resolved.
* The analysis phase failed for "MyHPHOST:/".
* Analysis and Execution had errors.
ERROR: More information may be found in the agent logfile using the
command "swjob -a log MyHPHOST-0433 @ MyHPHOST:/".
======= 08/21/13 14:31:03 METDST END swinstall SESSION
(non-interactive) (jobid=MyHPHOST-0433)
root@MyHPHOST:/hroot#
*** Failed becasue of dependencies. To overcomes this, evaluate the dependency condition and exclude it if possible
root@MyHPHOST:/hroot# swinstall -s MyHPHOST2:/var/opt/pkgs/depots/Rel.11.31/apps -x enforce_dependencies=false NMSAP
root@MyHPHOST:/hroot# swlist -l product | grep NMSAP
NMSAP 4.0 NetWorker Module for SAP with Oracle
root@MyHPHOST:/hroot#
Wednesday, October 10, 2012
FTP site command
UMASK for ftp can be set globally by adding the proper value for umask in the file /etc/ftpd/ftpaccess
But how can umask be used from a client system to be executed on the remote server instead of the global setting?
To send some commands from client to server where it can be executed.
For eg) To set UMASK for a user on the remote server, use
ftp> site UMASK
SITE command can be used for a number of other operations as well as seen in the ftp help menu
ftp> site help
214-The following SITE commands are recognized (* =>'s unimplemented).
UMASK GROUP INDEX GROUPS
IDLE GPASS EXEC CHECKMETHOD
CHMOD NEWER ALIAS CHECKSUM
HELP MINFO CDPATH
214 Direct comments to ftp-bugs@solaris1.
ftp>
Friday, September 28, 2012
Pluggable Authentication Module (PAM)
PAM allows various authentication technologies such as Kerberos, RSA, smart cards and DCE into system entry services such as login, passwd, rlogin, telnet, ftp, and su without changing any of these services.
PAM configuration file pam.conf is used to manage how these services use PAM framework.
How it works?
Application Services (rlogin, telnet, ssh etc...) => PAM API (Refers pam.conf) => PAM Modules to manage the access
The entries in /etc/pam.conf or in PAM policy files are in one of the following formats:
"service-name module-type control-flag module-path module-options"
eg) LDAP configuration in pam.conf.
more /etc/pam.conf | grep ldap
zone03:/root# more /etc/pam.conf | grep ldap
login auth required pam_ldap.so.1 use_first_pass
rlogin auth required pam_ldap.so.1 use_first_pass
rsh auth required pam_ldap.so.1 use_first_pass
ppp auth required pam_ldap.so.1 use_first_pass
other auth required pam_ldap.so.1 use_first_pass
passwd auth required pam_ldap.so.1 use_first_pass
User Creation issues and some checks
(zone01:/)# useradd -u 890 -g 52 -d /twsp/tws -c "Master user" -s /bin/ksh Master
UX: useradd: ERROR: group 582 does not exist. Choose another.
(zone01:/)# groupadd -g 52 twspgr
(zone01:/)# useradd -u 890 -g 52 -d /twsp/tws -c "Master user" -s /bin/ksh Master
UX: useradd: ERROR: Inconsistent password files. See pwconv(1M).
(zone01:/)#
(zone01:/)# pwconv
(zone01:/)#
(zone01:/)# useradd -u 890 -g 52 -d /twsp/tws -c "Master user" -s /bin/ksh Master
UX: useradd: ERROR: Inconsistent password files. See pwconv(1M).
(zone01:/)# cat /etc/passwd |grep Master
(zone01:/)# useradd -u 890 -g 52 -d /twsp/tws -c "Master user" -s /bin/ksh Master
UX: useradd: ERROR: Inconsistent password files. See pwconv(1M).
(zone01:/)#
(zone01:/)# wc -l /etc/passwd /etc/shadow
27 /etc/passwd
27 /etc/shadow
54 total
(zone01:/)# pwck
uucp:x:5:5:uucp Admin:/usr/lib/uucp:
Login directory not found
nuucp:x:9:9:uucp Admin:/var/spool/uucppublic:/usr/lib/uucp/uucico
Login directory not found
Optional shell file not found
(zone01:/)#
(zone01:/)#
(zone01:/)# ls -ld /usr/lib/uucp
/usr/lib/uucp: No such file or directory
(zone01:/)# grpck
utlitygr::360:cdpuck,cdpucka,cdpucks,cdpuckm
Group name too long
(zone01:/)#
(zone01:/)#
(zone01:/)# ls /var/spool/uucppublic
/var/spool/uucppublic: No such file or directory
(zone01:/)# ls /usr/lib/uucp/uucico
/usr/lib/uucp/uucico: No such file or directory
(zone01:/)#
Wednesday, September 19, 2012
hacf -cftocmd to recreate the commands from the main.cf file
The whole VCS config can be recreated by recreating the commands from the main.cf file.
Location of config file - /etc/VRTSvcs/conf/config
dump the exsisting config details in the memory to the disk.
(Solaris1:/root)# cd /etc/VRTSvcs/conf/config
(Solaris1:/etc/VRTSvcs/conf/config)# haconf -dump
(Solaris1:/etc/VRTSvcs/conf/config)#
now create the command file from the main.cf file using the hacf command
(Solaris1:/etc/VRTSvcs/conf/config)# hacf
VCS INFO V-16-1-10601 Usage:
hacf -cftocmd
hacf -cmdtocf
hacf -verify
hacf -help
(Solaris1:/etc/VRTSvcs/conf/config)#
This command will create the command file whioch can be used to recreate the whole cluster.
hacf -cftocmd
(Solaris1:/etc/VRTSvcs/conf/config)# hacf -cftocmd . -dest .
(Solaris1:/etc/VRTSvcs/conf/config)# ls -ltr | tail
-rw------- 1 root root 29075 Nov 13 14:31 main.cf.13Nov2012.14.31.22
-rw------- 1 root root 29362 Nov 26 12:32 main.cf.26Nov2012.12.32.09
-rw------- 1 root root 30286 Nov 27 11:35 main.cf.27Nov2012.11.35.18
-rw------- 1 root root 30649 Dec 24 10:27 main.cf.24Dec2012.10.27.42
-rw------- 1 root root 30722 Dec 24 10:29 main.cf.24Dec2012.10.29.13
-rw------- 2 root root 33096 Feb 25 14:34 main.cf.previous
-rw------- 2 root root 33096 Feb 25 14:34 main.cf.25Feb2013.14.34.29
-rw------- 2 root root 33099 Mar 26 11:22 main.cf.26Mar2013.11.22.57
-rw------- 2 root root 33099 Mar 26 11:22 main.cf
-rw------- 1 root root 192090 Mar 26 11:23 main.cmd
(Solaris1:/etc/VRTSvcs/conf/config)#
(Solaris1:/etc/VRTSvcs/conf/config)# more main.cmd
haclus -modify PrintMsg 0
haclus -modify UserNames alex bIGmJLhRJfIReHFgFI bibon ejjEjpInjEgkFg sarco JlmKliLilFljKslNltKglFmh
KulS indigo dKLjKFjQKiKSjHKmKF naglel aHHoHCgIHjHQhEEbED idone cpoLpyOxpJpvLkmKmmKn z_zone1
_Solaris1 chhPilGqhOedDdeAed
haclus -modify ClusterAddress "10.20.02.180"
haclus -modify Administrators alex bibon sarco indigo naglel idone
haclus -modify SourceFile "./main.cf"
haclus -modify ClusterName vcs-cluster1
hatype -add ASG
hatype -modify ASMDG SourceFile "./OracleMTypes.cf"
hatype -modify ASMDG AgentDirectory "/opt/VRTSagents/ha/bin/ASG"
hatype -modify ASMDG ArgList Sid Owner Home DBAUser DBAPword DiskGroups EnvFile Encoding
hatype -modify ASMDG ContainerOpts RunInContainer 1 PassCInfo 0
haattr -add ASG Home -string
haattr -add ASG Owner -string
Thursday, September 13, 2012
recoveryoption parameter setting in VXVM
Changing VxVM parameter in order to improve the reaction of the Solaris x86 servers in case of SAN instabilities.
Veritas level configuration changes to be done on the hosts Solaris1 and
Solaris1.
There is no impact as it is an online activity
(Solaris1:/root)#
(Solaris1:/root)# vxdmpadm getattr enclosure hp_p95000
ENCLR_NAME ATTR_NAME DEFAULT CURRENT
============================================================================
hp_p95000 iopolicy MinimumQ MinimumQ
hp_p95000 partitionsize 512 512
hp_p95000 use_all_paths - -
hp_p95000 failover_policy Global Global
hp_p95000 recoveryoption[throttle] Nothrottle[0] Nothrottle[0]
hp_p95000 recoveryoption[errorretry] Timebound[300] Timebound[300]
hp_p95000 redundancy 0 0
hp_p95000 dmp_lun_retry_timeout 0 0
hp_p95000 failovermode - -
(Solaris1:/root)# vxdmpadm listenclosure all
ENCLR_NAME ENCLR_TYPE ENCLR_SNO STATUS ARRAY_TYPE LUN_COUNT
=======================================================================================
disk Disk DISKS CONNECTED Disk 4
hp_xp24k5 HP_XP24K 28494 CONNECTED A/A 199
hp_p95000 HP_P9500 85753 CONNECTED A/A 127
(Solaris1:/root)#
(Solaris1:/root)# vxdmpadm getattr enclosure hp_p95000
ENCLR_NAME ATTR_NAME DEFAULT CURRENT
============================================================================
hp_p95000 iopolicy MinimumQ MinimumQ
hp_p95000 partitionsize 512 512
hp_p95000 use_all_paths - -
hp_p95000 failover_policy Global Global
hp_p95000 recoveryoption[throttle] Nothrottle[0] Nothrottle[0]
hp_p95000 recoveryoption[errorretry] Timebound[300] Timebound[300]
hp_p95000 redundancy 0 0
hp_p95000 dmp_lun_retry_timeout 0 0
hp_p95000 failovermode - -
(Solaris1:/root)#
(Solaris1:/root)#
(Solaris1:/root)# vxdmpadm getattr enclosure hp_xp24k50
ENCLR_NAME ATTR_NAME DEFAULT CURRENT
============================================================================
hp_xp24k50 iopolicy MinimumQ MinimumQ
hp_xp24k50 partitionsize 512 512
hp_xp24k50 use_all_paths - -
hp_xp24k50 failover_policy Global Global
hp_xp24k50 recoveryoption[throttle] Nothrottle[0] Nothrottle[0]
hp_xp24k50 recoveryoption[errorretry] Timebound[300] Timebound[300]
hp_xp24k50 redundancy 0 0
hp_xp24k50 dmp_lun_retry_timeout 0 0
hp_xp24k50 failovermode - -
(Solaris1:/root)#
(Solaris1:/root)#
(Solaris1:/root)# vxdmpadm setattr enclosure hp_p95000 recoveryoption=timebound iotimeout=320
(Solaris1:/root)#
(Solaris1:/root)# vxdmpadm getattr enclosure hp_xp24k50
ENCLR_NAME ATTR_NAME DEFAULT CURRENT
============================================================================
hp_xp24k50 iopolicy MinimumQ MinimumQ
hp_xp24k50 partitionsize 512 512
hp_xp24k50 use_all_paths - -
hp_xp24k50 failover_policy Global Global
hp_xp24k50 recoveryoption[throttle] Nothrottle[0] Nothrottle[0]
hp_xp24k50 recoveryoption[errorretry] Timebound[300] Timebound[300]
hp_xp24k50 redundancy 0 0
hp_xp24k50 dmp_lun_retry_timeout 0 0
hp_xp24k50 failovermode - -
(Solaris1:/root)# vxdmpadm getattr enclosure hp_p95000
ENCLR_NAME ATTR_NAME DEFAULT CURRENT
============================================================================
hp_p95000 iopolicy MinimumQ MinimumQ
hp_p95000 partitionsize 512 512
hp_p95000 use_all_paths - -
hp_p95000 failover_policy Global Global
hp_p95000 recoveryoption[throttle] Nothrottle[0] Nothrottle[0]
hp_p95000 recoveryoption[errorretry] Timebound[300] Timebound[320]
hp_p95000 redundancy 0 0
hp_p95000 dmp_lun_retry_timeout 0 0
hp_p95000 failovermode - -
(Solaris1:/root)#
(Solaris1:/root)#
(Solaris1:/root)# vxdmpadm setattr enclosure hp_xp24k50 recoveryoption=timebound iotimeout=320
(Solaris1:/root)# recoveryoption=timebound iotimeout=320
(Solaris1:/root)#
(Solaris1:/root)#
(Solaris1:/root)# vxdmpadm getattr enclosure hp_xp24k50
ENCLR_NAME ATTR_NAME DEFAULT CURRENT
============================================================================
hp_xp24k50 iopolicy MinimumQ MinimumQ
hp_xp24k50 partitionsize 512 512
hp_xp24k50 use_all_paths - -
hp_xp24k50 failover_policy Global Global
hp_xp24k50 recoveryoption[throttle] Nothrottle[0] Nothrottle[0]
hp_xp24k50 recoveryoption[errorretry] Timebound[300] Timebound[320]
hp_xp24k50 redundancy 0 0
hp_xp24k50 dmp_lun_retry_timeout 0 0
hp_xp24k50 failovermode - -
(Solaris1:/root)# vxdmpadm getattr enclosure hp_p95000
ENCLR_NAME ATTR_NAME DEFAULT CURRENT
============================================================================
hp_p95000 iopolicy MinimumQ MinimumQ
hp_p95000 partitionsize 512 512
hp_p95000 use_all_paths - -
hp_p95000 failover_policy Global Global
hp_p95000 recoveryoption[throttle] Nothrottle[0] Nothrottle[0]
hp_p95000 recoveryoption[errorretry] Timebound[300] Timebound[320]
hp_p95000 redundancy 0 0
hp_p95000 dmp_lun_retry_timeout 0 0
hp_p95000 failovermode - -
(Solaris1:/root)#
(Solaris1:/root)# vxdmpadm getattr enclosure hp_xp24k50 | grep Timebound
hp_xp24k50 recoveryoption[errorretry] Timebound[300] Timebound[320]
(Solaris1:/root)# vxdmpadm getattr enclosure hp_p95000 | grep Timebound
hp_p95000 recoveryoption[errorretry] Timebound[300] Timebound[320]
(Solaris1:/root)#
(Solaris1:/root)# vxdmpadm getattr enclosure hp_xp24k50 | grep Timebound; vxdmpadm getattr enclosure hp_p95000 | grep Timebound
hp_xp24k50 recoveryoption[errorretry] Timebound[300] Timebound[320]
hp_p95000 recoveryoption[errorretry] Timebound[300] Timebound[320]
(Solaris1:/root)#
Subscribe to:
Posts (Atom)