Hardware, Software and Connectivity Checks Check Node Performance 1-
2345-
678910-
1- Check Check the status status of the node node in the the cluster cluster.. C:\>prcstate Print out disk states. C:\>raidutil -L all. Reaction: If the printout shows a RAID or disk status other than Optimal, or the firmware is different from “FT06”, then contact 2 nd Line Support. Print st status lilist of of al all av available no nodes in in th the cl cluster. C:\>cluster node Prin Printt stat statu us list list of all ava availa ilable ble reso esourc urce groups in the clus clustter. er. C:\>cluster group Print st status list of all availa ilable resources in the cluster ter. C:\>cluster res Print the list of all AP users and user groups. C:\>net user C:\>net localgroup NOTE: command “userdump” may be used to printout a detailed list of users and groups definition. Check status of Function Change. C:\>fchstart –V Print the Backup parameters. C:\>bupprint –a Prin Printt th the pro process cess contr ntrol in ser service vice perfo erforrmance log with ith ana analys lysis. is. C:\>ispprint –a Prin Printt the the cont conten entt of of th the reg regis istr trat atio ion n fil file e tha thatt is is a part art of of the the Dire Direct ctor ory y Ser Servi vice ce func functi tion on.. C:\>dsdls -a Action: Check for for the existen tence of alarms on the AP. C:\>alist
Check Node Communication 123-
Printout IPNs present in the system C:\>ipnaadm –list Printout at attributes of of al all co connected CP CP-AP channels. C:\>cpdtest –c Printout a long list of of th the at attributes of of al all ac active Ads. C:\>cpdlist –l
Basic AP-CP MML checks 1. Open Open an mml command command session session with with receptio reception n of spontaneo spontaneous us printouts printouts.. C:\>mml –a 2. Print Print logical logical to to physical physical RP bus bus branch branch alloca allocation tion..
10. Print the Printout Routing Table (PRCA).
AP SW Status and Configuration 1) Print Cluster Site Parameters. C:\>spchange –dis 2) Check which computers belong to the current domain. C:\>net view 3) Check that LMHOSTS file is correct. C:\>nbtstat -c 4) Print SW status. C:\>swrprint 5) Print all started System Services. C:\>net start NOTE: Some of the most critical services are: Cluster Server ACS_FCH_Server Netlogon burServer IIS Admin Service FTP Publishing Service pcAnywhere Host Service
6) Check IPN SW available on the AP. C:\>dir C:\TFTPBOOT 7) Check the configuration files for the IPNs (X is the number of the IPN to be checked.) C:\>type C:\TFTPBOOT\boot.ipnX 8) Print all virtual directories on the standard FTP site. C:\>vdls –n "Default FTP Site" 9) Print all the defined associations between AP groups and CP user codes. C:\>cuals 10) Check that the CP users and administrators belong to either the CPADMG or CPUSRG local groups. C:\>net user 11) Print the multiple time zone link for the time zone category in the CP. C:\mtzln –p 12) Print the current date and time. C:\>date /T C:\>time /T Reaction 1a: The date needs to be modified. C:\>date NOTE: You will be prompted to introduce the correct date. Reaction 1b: The time needs to be modified. C:\>time NOTE: You will be prompted to introduce the correct time.
Reaction 2: Only the BDC’s date or time needs to be modified. C:\>net time /DOMAIN /SET Reaction 3: The current node should be synchronized against the other one. C:\>net time \\ /SET
NOTE2: Some important folders to check are: C:\Program Files C:\inetsrv C:\acs K:\images (only active node) L:\FMS\data\tmp\smo (only active node)
Checks for Active Node only 1. 2. 3. 4.
Action: Print status and attributes of the audit log. C:\>aloglist Action: Check that volume RELVOLUMSW exists. C:\>dir "K:\FMS\data\CPF" Action: Check that the exchange volumes exist. C:\>dir "K:\FMS\data\CPF\RELVOLUMSW" Action: Check that the exchange data volume for IN Management exists. C:\>dir "L:\FMS\data\CPF\EXCHVOLUME"
Charging Check 1. 2.
Action: Print the value for SAE 500 on block CHOP. C:\>mml SAAEP:BLOCK=CHOP,SAE=500; Verify that charging data is being received from the CP. The “lastMessNo” should be increasing to indicate charging data is being received from the CP. The “lastAckMess” should be increasing to indicate charging data is being fetched by the billing subsystem (RDT/FOS). The “lastMessNo” should be greater than or equal to the “lastAckMess”. The msdls command should be repeated several times to confirm the “lastMessNo” is increasing. C:\>msdls -m CHS -s cp0ex
3.
4.
MessageStore Name can be: CHS Verify charging data is being processed by the billing subsystem. C:\>rdtview -s Verify charging is being transferred to the billing centre. C:\>rdtview -b
STS Check i. Action: Print configuration data of STS object types. C:\>stmotls -l ii. Action: Print states of STS measuring programs. C:\>stmmp -L
