Professional Documents
Culture Documents
2007-03-08
Page 1 of 24
Contents 1 System Information....................................................................................4 2 Error printouts............................................................................................4 2.1 AP not redundant.............................................................................4 2.2 Not enough rights to run Audit script................................................4 2.3 Node names include illegal characters.............................................5 2.4 Node names are 15 characters or longer.........................................5 2.5 Cluster node names faulty................................................................5 2.6 Differences between A-nodes and B-nodes swrprint......................5 2.7 Repair fix R1.1 incorrectly installed..................................................5 2.8 Security patch S2.4 incorrectly installed...........................................5 2.9 No shutdown detected after R1.1 installation...................................5 2.10 Incorrectly installed applications.....................................................6 2.11 Non-default user profile in Pragma Telnet server found.................6 2.12 System variable COMPUTERNAME is faulty.................................6 2.13 Italian keyboard layout used...........................................................6 2.14 Empty User variable Path...............................................................6 2.15 NT4: Backup.FTS is missing........................................................6 2.16 Directories that should be files.......................................................7 2.17 Legal notice is displayed at logon...................................................7 2.18 AP alarm list not empty...................................................................7 2.19 AP maintenance data not normal...................................................7 2.20 AM firmware version is too low.......................................................7 2.21 Watchdog is not enabled................................................................7 2.22 AM boards communication not normal...........................................7 2.23 An account other than built-in Administrator is called Administrator .................................................................................................8 2.24 User is member of Guests or Domain Guests................................8 2.25 Expiry date is set on user account..................................................8 2.26 RAID firmware is too old.................................................................8 2.27 Mismatch in RAID firmware between nodes...................................8 2.28 Cluster support not enabled in RAID..............................................8 2.29 Mirrored disks not redundant..........................................................9 2.30 NT4: IIS database enum metadata is corrupt.................................9 2.31 FTP Server root directory in wrong folder.......................................9 2.32 FTP Server virtual directory incorrectly defined..............................9 2.33 FTP Server virtual directories differ between nodes.......................9 2.34 Anonymous FTP access incorrectly set..........................................9 2.35 FTP logging is incorrectly set.......................................................10 2.36 WinS03: Recovery console folder missing....................................10 2.37 NT4: M:\Images exists in NT4......................................................10 2.38 NT4: M:\ exists in NT4 AP2..........................................................10 2.39 Corrupt ACL in active node - Account Domain not found.............10 2.40 Corrupt ACL in passive node - Account Domain not found...........11 2.41 Corrupt ACL in active node - Unexpected or missing ACE...........11 2.42 Corrupt ACL in passive node - Unexpected or missing ACE........11
2007-03-08
Page 2 of 24
2.43 Startup parameters for Distinct TFTP faulty..................................11 2.44 Partition missing from the system disk.........................................12 2.45 NT4: Partition on system disk has wrong file system....................12 2.46 Partition with faulty size on system disk........................................12 2.47 Partition with faulty label on system disk......................................12 2.48 NT4: System disk partition layout cannot be verified....................12 2.49 NT4: F-drive is too small...............................................................12 2.50 Free space limit reached..............................................................13 2.51 WinS03: Dirty bit set on volume....................................................13 2.52 Large DDI-files.............................................................................13 2.53 Persistent network connections found..........................................13 2.54 Wrong hosts file used...................................................................13 2.55 Cluster nodes not normal.............................................................13 2.56 Cluster group not online...............................................................13 2.57 Ownership of cluster groups not normal.......................................14 2.58 Preferred owners for RGAPM_# groups are incorrect..................14 2.59 Ownership of cluster groups differ between nodes.......................14 2.60 Cluster resources not online.........................................................14 2.61 Cluster network interfaces not normal..........................................14 2.62 Public cluster network interface has wrong name.........................14 2.63 NT4: DHCP backup directory contains old sub-directory............14 2.64 NT4: DHCP backup could be corrupt...........................................15 2.65 NT4: Domain communication faulty..............................................15 2.66 WinS03: Nodes missing from DC list............................................15 2.67 WinS03: PDC not found...............................................................15 2.68 WinS03: FSMO roles not normal..................................................15 2.69 WinS03: NTDS parameters differ between nodes........................15 2.70 WinS03: Old frconfig version has been used................................16 2.71 WinS03: Wrong node name in Frconfig.log..................................16 2.72 WinS03: Last Frconfig attempt failed............................................16 2.73 WinS03: AD replication status is faulty.........................................16 2.74 WinS03: Owner of Global Catalog is incorrect..............................16 2.75 WinS03: AD replication disabled..................................................16 2.76 WinS03: USN times are more than 60 minutes apart...................17 2.77 WinS03: Command dsquery computer has failed......................17 2.78 WinS03: AD objects differ between nodes....................................17 3 Warning printouts.....................................................................................18 3.1 Large time gap between log files....................................................18 3.2 Conflicting APM and/or APIO information.......................................18 3.3 NT4: Telnet server version.............................................................18 3.4 NTDS registry key in NT4...............................................................18 3.5 Timezone differ between the nodes................................................18 3.6 Timezone differ between CP and AP..............................................18 3.7 No timezone link.............................................................................19 3.8 IPNA not connected.......................................................................19 3.9 IPN link is blocked..........................................................................19 3.10 IPN software revision differ between CP and AP..........................19 3.11 IPN software revision differ between AP-nodes............................19 3.12 IPNX, IPNA and/or IPNAX boards have too low revision..............19 3.13 CP memory congestion................................................................19 3.14 High temperature on AM or PSU boards......................................20 3.15 Locked user account found..........................................................20 3.16 Disabled user account found........................................................20 3.17 Mismatch in RAID firmware between swrprint and raidutil............20 3.18 Wrong file attributes in C:\............................................................20 3.19 Wrong file attributes in E:\............................................................20
2007-03-08
Page 3 of 24
3.20 Low free RAM...............................................................................21 3.21 Pagefile too small.........................................................................21 3.22 Pagefile too large.........................................................................21 3.23 Memory leaks...............................................................................21 3.24 Handle leaks.................................................................................21 3.25 Services have wrong startup state................................................21 3.26 Services not started by service account.......................................22 3.27 Services registered by wrong account..........................................22 3.28 setupservices.def is faulty............................................................22 3.29 AP backup too old or corrupt........................................................22 3.30 Old virus definitions......................................................................22 3.31 NT4: lmhosts file does not match Remote Cache Name Table....22 3.32 NT4: lmhosts file corrupt...............................................................22 3.33 Ping test between nodes failed.....................................................23 3.34 CP users and AP user groups not associated..............................23 3.35 AD-devices have queued printouts...............................................23 3.36 RELFSW0 is not newest in stack..................................................23 3.37 Too few CP reload files................................................................23 3.38 CP reload file missing...................................................................23 3.39 CP middleware does not match RELFSW0..................................23 3.40 DHCP Server client types faulty...................................................24 3.41 DHCP Server broadcast flag faulty...............................................24 3.42 User- or Core memory dumps found............................................24 3.43 Max size of one or more event logs is faulty.................................24
2007-03-08
Page 4 of 24
System Information
Various information about the system is derived from the following commands in the AP Audit script:
hostname date /t time /t hwver ver prcstate set cluster /ver swrsid h swrprint type C:\temp\hfix.log |findstr HKEY && del C:\temp\hfix.log type C:\temp\tz.log && del C:\temp\tz.log mml IOEXP; mml SAOSP; fcc_getbib "C:\Program Files\Dptmgr\Raidutil" K fcc_amversion own (only on WinS03) cd /d "C:\Program Files\force\AM_Services\" && fcc_amtest own -f
(only on NT4)
type %computername%.txt (only on NT4) wmic MEMLOGICAL GET AvailableVirtualMemory, TotalPageFileSpace, TotalPhysicalMemory, TotalVirtualMemory (only on WinS03) wmic PAGEFILE GET (only on WinS03) tasklist (only on WinS03)
Error printouts
Error printouts are always generated for every error found in the AP Audit Script log files. Every error printout is preceded by a prompt:
>>> >>>
2.1
AP not redundant
Printout from:
prcstate
2.2
2007-03-08
Page 5 of 24
2.3
Only characters A-Z, 0-9 and - are allowed. Any other character can cause OS Upgrade (NT4 to WinS03) to fail and can also cause cluster and/or domain communication problems.
2.4
Due to a bug in APZ 12.0 BURBIN version R5G and older, burbackup will fail if node name is 15 characters or longer.
2.5
2.6
2.7
Checks if R1.1 is installed after S3.2, but only if R1.9 has not been installed.
2.8
2.9
Checks that a reboot has been initiated between the installations of R1.1 and S3.2.
2007-03-08
Page 6 of 24
2.10
2.11
Any non-default profile will trigger this error printout. A non-default profile can cause upgrade OPS-scripts to fail.
2.12
2.13
For NT4, this can cause OSU (upgrade to WinS03) to fail. For WinS03, this can cause unpredictable behaviour in Telnet and SSH sessions.
2.14
An empty user variable called Path can cause OS Upgrade (NT4 to WinS03) to fail.
2.15
(only on NT4)
A missing Backup.FTS file in C:\Winnt\System32 can cause OS Upgrade (NT4 to WinS03) to fail.
2007-03-08
Page 7 of 24
2.16
Certain directories that really should be files can among other things cause OS Upgrade (NT4 to WinS03) to fail.
2.17
A legal notice displayed at logon can cause the automated upgrade script for OS Upgrade to fail.
2.18
2.19
2.20
(only on NT4) AM firmware version does not match the LBB version.
2.21
AM watchdog is disabled.
2.22
2007-03-08
Page 8 of 24
2.23
2.24
Users with membership in local group Guests or global group Domain Guests are listed. Such membership can cause OS Upgrade to fail and can also have negative impact on e.g. running certain commands.
2.25
User accounts with expiry date set are listed. A user account that expires during performing an upgrade can cause unpredictable behaviour.
2.26
(only on APG40C/2)
2.27
on APG40C/4)
2.28
(only on APG40C/2)
2007-03-08
Page 9 of 24
2.29
2.30
2.31
2.32
2.33
2.34
Anonymous access must be disabled for Default FTP Site and enabled for the two APIO_# servers.
2007-03-08
Page 10 of 24
2.35
Logging should be enabled for Default FTP Site and disabled for the two APIO_# servers.
2.36
(only on WinS03)
The recovery console folder cmdcons is missing from E:\. This will disable the use of the recovery console and DAT tape during disaster recovery.
2.37
2.38
2.39
Files and folders with <Account Domain not found> in their ACL:s in the active node are listed.
2007-03-08
Page 11 of 24
2.40
Files and folders with <Account Domain not found> in their ACL:s in the passive node are listed.
2.41
Files and folders with inconsistent ACL:s in the active node are listed. N.B! Only the root folder of all volumes, except for E:\ where the files in root folder are checked if Everyone have full access, and the first two directory levels of all volumes on the data disks are analysed.
2.42
Files and folders with inconsistent ACL:s in the passive node are listed. N.B! Only the root folder of all volumes is analysed, except for E:\ where the files in root folder are checked if Everyone have full access.
2.43
The file win.ini contains wrong parameters for Distinct TFTP, regarding the APZ version.
2007-03-08
Page 12 of 24
2.44
2.45
(only on NT4)
One or more volumes on the system disk have non-NTFS file system.
2.46
2.47
2.48
(only on NT4)
Sizes and setup of ntserv and ntbackup partitions does not match the default configuration. This can be a sign of partition alignment being out of order. This needs to be verified by using GUI Disk Administrator or CLI partinfo or partitionnt. N.B! If a previous OS upgrade attempt has been made and a fallback has occurred, the partition configuration will no longer match the default configuration.
2.49
(only on NT4)
2007-03-08
Page 13 of 24
2.50
Volumes that have reached their limit of free space are listed.
2.51
(only on WinS03)
2.52
Large DDI-files
Printout from: dir c:\bur (only on NT4) dir c:\acs\data\bur (only on WinS03) DDI-files with size larger than 500 kB for NT4 and 1 MB for WinS03 are listed.
2.53
Network connections that require different logon credentials will cause the GUI to wait for password to that network connection before logon procedure continues. If the built-in Administrator account has such persistent network connections defined, this will cause automated logon in OS Upgrade to fail.
2.54
hosts file contents does not match the connected APZ type.
2.55
2.56
2007-03-08
Page 14 of 24
2.57
2.58
The A-node must be preferred owner from RGAPM_0 and B-node must be preferred owner for RGAPM_1. If wrong or no owner is listed, FCH might fail.
2.59
Lists all cluster groups with information about owner derived from both nodes.
2.60
2.61
2.62
2.63
2007-03-08
Page 15 of 24
2.64
2.65
A-node is not PDC or B-node is not BDC or secure channel not set up correctly.
2.66
2.67
2.68
2.69
2007-03-08
Page 16 of 24
2.70
Frconfig version older than 1.4.0 build 3 has been used. This could cause AD replication problems.
2.71
Last change done by frconfig does not show current node name.
2.72
2.73
One or more recent AD replication attempts has failed or status could not be shown.
2.74
2.75
2007-03-08
Page 17 of 24
2.76
USN time stamps differ more than 60 minutes between the nodes. This could mean that AD replication is not working even if replication status shows OK.
2.77
2.78
2007-03-08
Page 18 of 24
Warning printouts
Warning printouts are generated for every warning (minor error) found in the AP Audit Script log files, but are omitted if ALAN is run in errors-only mode. Every warning printout is preceded by a prompt:
>>>
3.1
The time stamp in the log files differ more than 60 minutes.
3.2
There is more than one entry for APM and/or APIO in the software product list.
3.3
A corrupt installation of telnet server can lead to swrprint showing Build 10 when in fact Build 7 is still installed.
3.4
3.5
3.6
2007-03-08
Page 19 of 24
3.7
No timezone link
Printout from:
mtzln p
3.8
At least one of ipna00 or ipna01 is missing in the printout. Check IPN data for any faults.
3.9
3.10
The boot.ipn# files contain other SW revision than whats loaded in CP.
3.11
3.12
One or more IPNX, IPNA and/or IPNAX boards in CP have a lower revision than recommended.
3.13
CP memory congestion
Printout from:
mml LABUP;
2007-03-08
Page 20 of 24
3.14
3.15
3.16
Listed accounts are disabled. Note: The accounts Guest and krbtgt and SUPPORT_388945a0 are not listed.
3.17
on APG40C/4)
3.18
The files in the root of C-drive have other than default attributes.
3.19
The files in the root of E-drive have other than default attributes.
2007-03-08
Page 21 of 24
3.20
3.21
3.22
3.23
Memory leaks
Printout from: pstat (only on NT) tasklist (only on WinS03) Listed processes use more memory than normal.
3.24
Handle leaks
Printout from: pstat (only on NT)
wmic PROCESS GET Processid, Name, ThreadCount, HandleCount, Priority, PageFaults, WorkingSetSize, QuotaNonPagedPoolUsage, QuotaPagedPoolUsage (only on WinS03)
Either the total handle count is too high or the listed processes have a higher handle count than normal.
3.25
(only
2007-03-08
Page 22 of 24
3.26
(only
on WinS03) Listed services should be started by the service account, but are not.
3.27
(only
on WinS03) Listed services should all be started by the same service account.
3.28
setupservices.def is faulty
Printout from:
type C:\Winnt\system32\setupservice.def | findstr /v #
The file setupservices.def does not contain all expected service names.
3.29
3.30
3.31
NT4: lmhosts file does not match Remote Cache Name Table
Printouts from:
nbtstat c type C:\winnt\system32\drivers\etc\lmhosts
The entries in lmhosts file does not match the Remote Cache Name Table.
3.32
2007-03-08
Page 23 of 24
3.33
If a timeout is received, warning is given that public interfaces might have communication problems.
3.34
3.35
3.36
CP reload file RELFSW0 is not the newest file in the reload stack.
3.37
3.38
3.39
2007-03-08
Page 24 of 24
3.40
The client types for the DHCP Server are not default.
3.41
(only on WinS03) The broadcast flag is incorrectly set with regards to APZ version.
3.42
3.43
The set maximum size of one or more event logs differs from the default value.