Changing HP ServiceGuard clustering parameters

orgdwprd@root:/etc/cmcluster> cmapplyconf -v -C dw_clx.conf
Begin cluster verification...
Checking cluster file: dw_clx.conf
Checking nodes ... Done
Checking existing configuration ... Done
Gathering storage information
Found 7 devices on node orgdwprd
Found 29 devices on node orgdwap1
Analysis of 36 devices should take approximately 6 seconds
0%----10%----20%----30%----40%----50%----60%----70%----80%----90%----100%
Found 3 volume groups on node orgdwprd
Found 4 volume groups on node orgdwap1
Analysis of 7 volume groups should take approximately 1 seconds
0%----10%----20%----30%----40%----50%----60%----70%----80%----90%----100%
Volume group /dev/lckdwvg is configured differently on node orgdwprd than on node orgdwap1
Volume group /dev/lckdwvg is configured differently on node orgdwap1 than on node orgdwprd
Volume group /dev/vgsap is configured differently on node orgdwprd than on node orgdwap1
Volume group /dev/vgsap is configured differently on node orgdwap1 than on node orgdwprd
Gathering network information
Beginning network prodwng (this may take a while)


orgdwprd@root:/etc/cmcluster> cmapplyconf -v -C dw_clx.conf
Begin cluster verification...
Checking cluster file: dw_clx.conf
Checking nodes ... Done
Checking existing configuration ... Done
Gathering storage information
Found 7 devices on node orgdwprd
Found 29 devices on node orgdwap1
Analysis of 36 devices should take approximately 6 seconds
0%----10%----20%----30%----40%----50%----60%----70%----80%----90%----100%
Found 3 volume groups on node orgdwprd
Found 4 volume groups on node orgdwap1
Analysis of 7 volume groups should take approximately 1 seconds
0%----10%----20%----30%----40%----50%----60%----70%----80%----90%----100%
Volume group /dev/lckdwvg is configured differently on node orgdwprd than on node orgdwap1
Volume group /dev/lckdwvg is configured differently on node orgdwap1 than on node orgdwprd
Volume group /dev/vgsap is configured differently on node orgdwprd than on node orgdwap1
Volume group /dev/vgsap is configured differently on node orgdwap1 than on node orgdwprd
Gathering network information
Beginning network prodwng (this may take a while)
Completed network prodwng
Cluster dw_CLX1 is an existing cluster
Modifying NODE_TIMorgUT value from 2000000 to 20000000 while cluster dw_CLX1 is running.
Cluster dw_CLX1 is an existing cluster
Checking for inconsistencies
Maximum configured packages parameter is 150.
Configuring 1 package(s).
149 package(s) can be added to this cluster.
200 access policies can be added to this cluster.
Modifying configuration on node orgdwprd
Modifying configuration on node orgdwap1
Modifying the cluster configuration for cluster dw_CLX1

Modify the cluster configuration ([y]/n)?
Marking/unmarking volume groups for use in the cluster
Unable to apply the configuration change: No such file or directory
. Check the syslog file(s) for additional information.
cmapplyconf: Unable to apply the configuration
orgdwprd@root:/etc/cmcluster>

Solaris: df: cannot statvfs - ERROR

OS: Sun Solaris 8/10
Hardware: Fire-V880

Error Message:

df: cannot statvfs /oracle/test/vol158: I/O error
df: cannot statvfs /oracle/test/vol159: I/O error
df: cannot statvfs /oracle/test/vol160: I/O error
df: cannot statvfs /oracle/test/vol161: I/O error
/dev/vx/dsk/testdg/vol16
142369792 140858696 1499360 99% /oracle/test/vol16
df: cannot statvfs /oracle/test/vol162: I/O error
df: cannot statvfs /oracle/test/vol163: I/O error
df: cannot statvfs /oracle/test/vol164: I/O error
df: cannot statvfs /oracle/test/vol165: I/O error
# vxprint -vt grep -i disabled
v vol125 - DISABLED ACTIVE 243609600 SELECT - fsgen
v vol158 - DISABLED ACTIVE 284774400 SELECT - fsgen
v vol159 - DISABLED ACTIVE 284774400 SELECT - fsgen
v vol160 - DISABLED ACTIVE 284774400 SELECT - fsgen
v vol161 - DISABLED ACTIVE 284774400 SELECT - fsgen
v vol162 - DISABLED ACTIVE 284774400 SELECT - fsgen
You may get errors on Filesystems and the volumes will get disabled automatically.
This may be due to intermittent connection loss with the Storage.
1. Try to enable the volume with command vxvol enable volxxx
2. Then check the state of the PLEX and if the plex state is in "Recover" State then,
make the plex "Clean" and "Stale" using the following script if you have multiple volumes

for i in `vxprint grep "Disk group:" awk '{ print $3 }'` ; do
for j in `vxprint -g $i grep "RECOVER" awk '{ print $2 }'` ; do
vxmend -g $i fix stale $j
vxmend -g $i fix clean $j
done
done
Reference:

http://support.veritas.com/docs/231913

+++++Post Your Queries related to HP-UX/SOlaris/VCS/VXVM - http://unixadvice.formyjob.net/ +++++++++

---------------------------------------------------------------------------------------------------------------------------------
Solaris 10 Zone Control Commands



The following control commands can be used to manage and monitor transitions between states:


• zlogin options zone-name

• zoneadm -z zone-name boot

• zoneadm -z zone-name halt
• zoneadm -z zone-name install
• zoneadm -z zone-name ready

• zoneadm -z zone-name reboot

• zoneadm -z zone-name uninstall

• zoneadm -z zone-name verify

• zonecfg -z zone-name: Interactive mode; can be used to remove properties of the following types: fs, device, rctl, net, attr

• zonecfg -z zone-name commit

• zonecfg -z zone-name create

• zonecfg -z zone-name delete

• zonecfg -z zone-name verify

Solaris 10 Zone Control Commands



The following control commands can be used to manage and monitor transitions between states:


• zlogin options zone-name

• zoneadm -z zone-name boot

• zoneadm -z zone-name halt

• zoneadm -z zone-name install

• zoneadm -z zone-name ready

• zoneadm -z zone-name reboot

• zoneadm -z zone-name uninstall

• zoneadm -z zone-name verify

• zonecfg -z zone-name: Interactive mode; can be used to remove properties of the following types: fs, device, rctl, net, attr

• zonecfg -z zone-name commit

• zonecfg -z zone-name create

• zonecfg -z zone-name delete

• zonecfg -z zone-name verify

Solaris 11 Reference:
http://solaristipsandtricks.blogspot.in/#!/2011/12/solaris-11-smf-and-nscd.html

Installing Ingress Controller - Kubernetes

Installing the Ingress Controller Prerequisites Make sure you have access to the Ingress controller image: For NGINX Ingress controll...