Replacing VCS Coordinator Disk while Veritas Cluster is Online

Hello Friends

The article describes "How to replace" the coordinator disk while Veritas cluster is running and SGs are ONLINE.

Caution :  In case any node leaves the cluster before the swap script completes; cluster may PANIC.

All the activities to be done on Cluster’s master node.

1.     Make sure system-to-system communication is functioning properly.

2.     Make sure that the cluster is online.

# vxfenadm -d

I/O Fencing Cluster Information:

================================

Fencing Protocol Version: 201

Fencing Mode: SCSI3

Fencing SCSI3 Disk Policy: dmp

Cluster Members:

                   * 0 (galaxy)

                   1 (nebula)

RFSM State Information:

                   node 0 in state 8 (running)

                   node 1 in state 8 (running)

3.     Import the coordinator disk group [The file /etc/vxfendg includes the name of the disk group] .

# vxdg -tfC import 'cat /etc/vxfendg'

              

            4. vxdg list vxfencoorddg |grep version

               If the version is below 140; it needs to be upgraded.

5          5. vxdg upgrade vxfencoorddg

6.     Turn off the coordinator attribute value for the coordinator disk group.

# vxdg -g vxfencoorddg set coordinator=off

7.     Initialize the new disks [/etc/vx/bin/vxdisksetup -i <disk_address> ]

8.     Add to the coordinator disk group. [vxdg -g vxfencoorddg adddisk <accessname>]

9.     Remove the old disks. [vxdg -g vxfencoorddg rmdisk <medianame>]

10.   Set the coordinator flag to on.[ vxdg -g vxfencoorddg set coordinator=on]

11.   Confirm the /etc/vxfenmode file is updated to specify the correct disk policy.

12.   Deport the Disk Group.

13.   From one node, start the vxfenswap utility. You must specify the diskgroup to the utility. [/opt/VRTSvcs/vxfen/bin/vxfenswap –g <DG>]

14.   If the disk verification passes, the utility reports success and asks if you want to commit the new set of coordinator disks.

Do you wish to commit this change? [y/n] (default: n) y

If the utility successfully commits, the utility moves the /etc/vxfentab.test file to the /etc/vxfentab file.

Solaris Print Request Outcome Codes definitions

Hello Friends

Below table represents the error codes meaning. The error code gets generated while printing OR if fails to print.

Information posted are compiled from the vendor site.

Outcome Code	Description
0x0001	The request was held pending resume.
0x0002	Slow filtering is running.
0x0004	Slow filtering finished successfully.
0x0008	The request is on the printer.
0x0010	File sent to Network Printer successfully.
0x0014	Filter applied successfully and file sent to printer.
0x0020	The request was held pending user change.
0x0040	The request was canceled.
0x0080	The request will print next.
0x0100	The request failed filtering or printing.
0x0200	The request is in transit to a remote printer (obsolete).
0x0400	The user will be notified.
0x0800	A notification is running.
0x1000	A remote system has accepted the request (obsolete).
0x2000	The administrator placed a hold on the request.
0x4000	The printer had to change filters.
0x8000	The request is temporarily stopped.