Veritas Pre-Check DocumentThis document is having all the necessary steps, which needs to be performed by every implementer SA before starting any activity on a VCS node(Dev/Test/Prod) and they must ensure that all required access has been given or enabled on all required nodes and all required information also been captured according to steps mentioned below.

1-The implementer SA must check his login access on Veritas Cluster via its Veritas Cluster Manager Console(GUI) and ensure that he is able to login and everything looks good, like below:

2- SA must check his login and sudo access on all assigned Veritas nodes and ensure that he is having proper sudo access to carryout the assigned task as per requirement and implementation given under the CR.

3-SA must check his login access into particular MGMT server and ensure that he is able to access the nodes via oconsole/rconsole

4-SA must check the schedule reboot time of all assigned nodes and disable the same, If this will conflict the CR’s window .

5-If we are going to make any change in configuration of VCS or AIX then every implementer SA must create a fresh mksysb before starting the activity.

6-Check the state of all nodes and status of all VCS Service groups by running the command “hastatus –sum”For Example:[pide123][/]#hastatus -sum

-- SYSTEM STATE-- System State Frozen

A pide122 RUNNING 0A pide123 RUNNING 0

-- GROUP STATE-- Group System Probed AutoDisabled State

B SAToolsgcasSG pide122 Y N ONLINE B SAToolsgcasSG pide123 Y N OFFLINE B SAToolsoracleSG pide122 Y N OFFLINE B SAToolsoracleSG pide123 Y N ONLINE B gcasSG pide122 Y N ONLINE B gcasSG pide123 Y N OFFLINE B ldapSG pide122 Y N OFFLINE B ldapSG pide123 Y N ONLINE B nicSG pide122 Y N ONLINE B nicSG pide123 Y N ONLINE B oracleSG pide122 Y N OFFLINE B oracleSG pide123 Y N ONLINE [pide123][/]#

7- Implementer SA must go through the AOTS CR’s implementation Plan, Validation Plan and Backout Plan and He also needs to ensure that all given steps and information are very much clear to him and he is ready and comfortable to start the change.

8- Implementer SA needs to check the error log, status of all PVs, status of all NON varied on and varied on VGs, status of all filesystems, out put of powermt display, powermt display dev=all /nas/fixes/aixftp/emc_path_chk –v command and ensure that everything looks good and there is no problem on the boxes, which are the part of your scheduled CR.

9- If you don’t have any required login access or access to Veritas Web Console as above then contact to our on-site resource and get it done before the schedule of your change request.

10-If any configuration changes are made via the GUI or command line, the changes must be saved by implementer SA and share the same information with PSA/BSA.

Note: TechM on-site resource also needs to check all required offshore access and the status of running Veritas Cluster, status of all service groups and status of nodes from OS perspective and ensure that everything is perfect before assigning any CR/TM to offshore resource.