Hardware, Software and Connectivity Checks

Check Node Performance

11- Check the status of the node in the 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 2nd Line Support. Print status list of all available nodes in the cluster. C:\>cluster node Print status list of all available resource groups in the cluster. C:\>cluster group Print status list of all available resources in the cluster. 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 Print the process control in service performance log with analysis. C:\>ispprint a Print the content of the registration file that is a part of the Directory Service function. C:\>dsdls -a Action: Check for the existence of alarms on the AP. C:\>alist Printout IPNs present in the system C:\>ipnaadm list Printout attributes of all connected CP-AP channels. C:\>cpdtest c Printout a long list of the attributes of all active Ads. C:\>cpdlist l 1. Open an mml command session with reception of spontaneous printouts. C:\>mml a 2. Print logical to physical RP bus branch allocation. <DPRBP; 3. Print IPN states and data. <OCINP:IPN=ALL; 4. Print the equipment connected to IPNs. <OCIEP:IPN=ALL; 5. Print list of the software modules loaded in the IPNs. <OCSIP:IPN=ALL; 6. Print AP maintenance and LAN data. <APAMP; 7. Print all applications and application specific data inserted in the configuration data table. <IOCDP; 8. Print the system standby device. <IOSYP; 9. Print the table of IO devices defined. <IOIOP:IO1=ALL;

2345-

678910-

Check Node Communication

123-

Basic AP-CP MML checks

10. Print the Printout Routing Table (PRCA). <IOROP; 11. Print the list of terminals, their terminal group and whether use of the terminal requires authority by the user. <IOTAP; 12. Check the status of hanging IO devices. <IOSTP; 13. Print the table of users, groups and authority option for all system users. <IOUAP:USER=ALL; 14. Action: Print the table of authorized categories for the terminal groups. <IOTGP; 15. Action: Check the existing CP backups. <SYBFP:FILE; 16. Action: Exit mml session. <EXIT;

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 <CP usr/adm username> 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 BDCs 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 \\<other node name> /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. Action: Print status and attributes of the audit log. C:\>aloglist 2. Action: Check that volume RELVOLUMSW exists. C:\>dir "K:\FMS\data\CPF" 3. Action: Check that the exchange volumes exist. C:\>dir "K:\FMS\data\CPF\RELVOLUMSW" 4. Action: Check that the exchange data volume for IN Management exists. C:\>dir "L:\FMS\data\CPF\EXCHVOLUME"

Charging Check
1. Action: Print the value for SAE 500 on block CHOP. C:\>mml SAAEP:BLOCK=CHOP,SAE=500; 2. 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 MessageStore Name can be: CHS 3. Verify charging data is being processed by the billing subsystem. C:\>rdtview -s 4. 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