PRODUCT_LINE: BCM ============================================ PreCheck Upgrade Tool version 1.0.5 Introduction ----------------- The BCM 3.6/3.7 to BCM 4.0 Pre-Check Tool is used to check if a particular BCM is compliant with Upgrade. The tool is run on a standard PC and uses a user friendly graphical interface. The Pre-Check Tool connects to the BCM being tested either over Dial-up or LAN interface, and produces a full compliance report which may be read on the client PC or can be retrieved later from the tested BCM. Pre-Check Tool may take few minutes to produce a full compliance report when run over LAN interface but it would approximately take 30 minutes if run over Dial-up interface. It can be run well in advance of any planned upgrade, allowing ample opportunity to perform whatever remedies might be necessary to make the BCM upgrade-compliant. Once the remedies have been performed, the tool can be used again to re-ascertain success. The Pre-Check Tool makes no changes to the BCM it is testing, and is not service interrupting. It does generation some output on the BCM but this will not affect the operation of the BCM. The Upgrade tool has a pre-check component as well, but it is designed to determine any failure cases, and immediately stop, preventing the Upgrade from proceeding. The Pre-Check Tool on the other hand performs as many tests as it can, even if it finds failure cases, generating as full a report as possible. Note: ------- Please refer to 'Installation' section for running Pre-Check Tool over Dial-up interface. -------------------------------------------------------------------------------- Requirements -------------------- The client PC must be running under one of the following supported Windows® operating systems: - Windows 98SE - Windows 2000 Professional - Windows XP (Professional and Home edition) The client PC must be able to communicate with the BCM either over Dial-up or LAN interface. While it is permissible to have multiple browsers installed, the client PC must have Internet Explorer 5.5, 6.0 or 7.0 installed as the Pre-Check tool makes use of some of the features provided by the Internet Explorer libraries. The client PC must contain a minimum of 150MB of free disk space for proper operation. -------------------------------------------------------------------------------- Installation (Packaging) -------------------------------- The Pre-Check Tool is distributed as a self-extracting executable. When this executable is run, it will un-package itself to a directory named PreCheck_X.Y.Z where X.Y.Z is the version of the Pre-Check tool. We will call this the PreCheck directory. This only need be done once. The Pre-Check tool may then be run by double-clicking the startup.bat file in the PreCheck directory, or the contents of the PreCheck directory may be burned to a CD and the tool will automatically run when inserted into a CD-ROM drive. IMPORTANT: ---------------- To run Pre-Check Tool from Shared Drive: ---------------------------------------- Pre-Check Tool can be run from Network Shared Drive provided it is mapped to the local PC. To run Pre-Check Tool over Dial-up connection: ---------------------------------------------- 1. Login credentials used to run Pre-check Tool should be a member of DialUpUserGroup. 2. Create Dialup outgoing interface on Client PC with same login credentials used in Step 1. 3. Configure Modem with analog line with an assigned Phone number. 4. Dial the number, use login credentials used in Step 1 and get connected to the BCM. 5. Run Pre-Check Tool on PC. Warnings: ------------- 1. Pre-Check Tool will take around 30-35 minutes to generate the report. 2. While executing Pre-Check Tool over Dial-up, all the tests will be completed over Dial-up interface and NOT over the LAN interface. There could be a chance where BCM may not be reachable over LAN interface. Just because Pre-Check Tool registered success over Dial-up, does not guarantee that the operator will be able to connect over LAN to do an upgrade. 3. BCM 4.0 Upgrade over Dial-up interface is not supported. -------------------------------------------------------------------------------- Running The BCM 3.6/3.7 to BCM 4.0 Pre-Check Tool ------------------------------ To run the Pre-Check Tool, the operator simply double-clicks the startup.bat file in the PreCheck directory created when the tool was installed (see "Installation".) The operator then provides the IP address of the BCM to be checked, and the admin user name and password, and then presses [Next] to continue. The progress of the Pre-Check is displayed in a scrollable window, and when the tool is finished, it will display a dialog box indicating if the Pre-Check passed or failed. In some cases it may not be possible to perform the tests, in which case a dialog box is presented explaining the condition. These are known as "fatal errors" and are not to be confused with a Pre-Check failure. List of Fatal Error Messages: ------------------------------------- 1. Invalid IP / Missing user / Missing password.Re-enter data then press "Start" or "Exit" 2. Connect failed. Invalid username or password.(check the username / password if the ee_admin password is not set to its default) 3. Connect failed. Unable to validate server. 4. Connect failed. Could not establish connection to network. 5. Connect failed. Please validate BCM information. (check if the IP address entered is correct) 6. Problem configuring FTP server on BCM. 7. Failed to create directories on BCM. 8. Problem uploading files. 9. Could not get working directory. 10. OnWizardNext premature return - hInternetSession == NULL 11. Failed to connect to FTP to transfer files. 12. Fail to send pre-check checksum file. Once the Pre-Check is done, in addition to providing the dialog box indicating pass or fail, the full compliance report is fetched from the BCM and stored on the operators PC as C:\Program Files\Nortel\PreCheckUpgrade\.txt where is the IP address of the tested BCM. The report may also be found on the BCM under C:\Upgrade\logs\PreCheck.txt. The files on the BCM and PC are overwritten each time the tool is run for the same IP address (BCM). Note: ----- Report file will not be generated in case of Fatal Errors. -------------------------------------------------------------------------------- Additional Info --------------------- - The last line of the report always indicates whether the Pre-Check passed or failed. - The report will indicate the date and time it was started. This comes from the BCM clock and so will reflect any time zone settings on the BCM. - The report on the BCM and the report on the operators PC differ by name only; the content is identical. - The Pre-Check tool requests a user name and password. Rather than require that the ee_admin user and its default password be enabled, the Pre-Check tool will permit you to input any valid administrative user and password for the purpose of running the Pre-Check. Because however, the Upgrade process requires the use of the ee_admin user and its default password, one of the tests performed is to test for access using the ee_admin user and its default password. If the ee_admin user/password do not permit access, it is recorded as a Pre-Check failure, and indicated in the report. Conversely, if the ee_admin user/password do permit access, the report reflects it. IMPORTANT: The Pre-Check Tool will by default try to use ee_admin/PlsChgMe! login credentials irrespective of the user supplied login credentials. - If ee_admin/PlsChgMe! User is enabled, Pre-Check Tool will continue further by ignoring the user supplied login credentials. - If ee_admin/PlsChgMe! User is not enabled, Pre-Check Tool will however continue further by using the user supplied login credentials. -------------------------------------------------------------------------------- Troubleshooting, Known Issues -------------------------------------------- - Running the Pre-Check Tool against a BCM that is not fully initialized or is performing a core upload will produce unpredictable results. This may be manifested as a failure to detect MSC card validity. This tool should only be run when the BCM is known to be fully initialized. - If you change the password for the admin user during the Pre-Check process, you will need to restart the BCM or you will get false reports of inability to configure the BCM's FTP server. - Network issues are the most common fault when the Pre-Check fails to run to completion. If you can't ping the BCM, or you can't connect to it using Internet Explorer, you cannot run the Pre-Check tool against it. Also be sure your firewall permits TCP and UDP connections on ports 443, 6800, 20, 21, 989 and 990. - "The Pre-Check Tool disappeared... now what?" This can sometimes be caused by software firewall solutions (such as CyberArmor). See the preceding bullet and be sure you have the correct ports opened. - The Pre-Check Tool consists of a number of files, all required for it to operate correctly. The tool checks for the existence of some of these files, but not all, so if you are experiencing unusual behaviour--especially if the tool doesn't produce any feedback when started--be sure you have the following files in the PreCheck directory (the directory created when you extracted the Pre-Check tool): - autorun.inf - prepfiles.lst - prepfolders.lst - startup.bat - STARTUP.PIF There will also be directories created under the PreCheck directory, specifically, directory 'config' and 'Nortel Networks\BCM\PrepFiles\Upgrade'. With the exceptions noted below, the files in these directories are checked for you so the full content is not listed here. In the 'config' directory, you should see the following files: - profiles.ini - BCM.upg - BCM Upgrade Wizard.exe Note that the Pre-Check Tool was based on the Upgrade Wizard, so the executable name has remained unchanged. In the 'Nortel Networks\BCM\PrepFiles' directory, ensure that the file 'prepfiles.crc' exists. Again, there are other files in the directory, but they are checked for you by the Pre-Check tool. -------------------------------------------------------------------------------- Handling Failure Conditions --------------------------------------- This section of the readme document contains a list of reported failure conditions, and what the operator can do to resolve them (if the issue is resolvable.) Message: ERROR:getValue CGI missing, cannot report status back to Pre-Check Wizard Explanation: Status reporting back to the Wizard requires the getValue CGI. If it doesn't exist, Pre-Check logs a fatal error and stops. Resolution: This is usually a problem with the Pre-Check tool missing some files. Re-extract the self-extracting executable (distribution) and re-try the Pre-Check. If it fails again, contact support. Message: ERROR:The BCM version is unsupported for this upgrade. Explanation: If Pre-Check can't determine the release, or the release is not BCM 3.6 or BCM 3.7, it reports a fatal error and stops. Resolution: The Pre-Check can only be run on a BCM 3.6 or BCM 3.7. Double check that the BCM being tested is indeed a BCM 3.6 or 3.7 and if it is not, the error message is intended behaviour; i.e., you cannot run Pre-Check on the BCM in question. If it is a BCM 3.6 or 3.7 however, Pre-Check is behaving incorrectly and you should contact support. Message: ERROR:PatchUtil.exe cannot be found, cannot run checksum on prepfiles. Explanation: Pre-Check checks for the existence of crc checker executable. If it can't be found, Pre-Check cannot checksum the files so it reports a fatal error and stops. Resolution: This is usually a problem with the Pre-Check tool missing the patchUtil.exe file, but it can also be caused by the file not being copied to the BCM correctly. Re-extract the self-extracting executable (distribution) and re-try the Pre-Check. If it fails again, contact support. Message: ERROR:prepfiles.crc cannot be found, cannot run checksum on prepfiles. Explanation: Pre-Check checks for the existence of the checksum file. If it can't be found, Pre-Check cannot checksum the files so it reports a fatal error and stops. Resolution: This is usually a problem with the Pre-Check tool missing the prepfiles.crc file, but it can also be caused by the file not being copied to the BCM correctly. Re-extract the self-extracting executable (distribution) and re-try the Pre-Check. If it fails again, contact support. Message: ERROR:Checksum failed on prepfiles. Explanation: If the checksum on the transferred files fails, the Pre-Check cannot be performed (this is the purpose of the checksum, to ensure file integrity) so Pre-Check reports a fatal error and stops. Resolution: This can be a problem with the checksum file itself (rare), or one or more of the 'prepfiles' was corrupted during transfer, or is corrupt in the Pre-Check directory. Re-extract the self-extracting executable and re-try the Pre-Check. If it fails again, contact support and inform them the checksum on the transferred files is failing. You may need a new self-extracting Pre-Check executable. Message: FAIL: Missing file ksuversion.typ which is needed to determine core load Explanation: Pre-Check verifies the existence of the ksuversion.typ file. It is not needed for the Pre-Check tool to work, but Upgrade will need it to determine what core load is present. If it's missing, Pre-Check reports a failure. Resolution: Log into the BCM serial console, or use VNC. Check for the existence of the file ksuversion.typ in folder f:\Program Files\Nortel Networks\Voice Solution\Data\ If it does not exist, contact support. If it does exist, try the Pre-Check again and contact support if it fails again. Message: ERROR:Inventory service not running, cannot continue. Explanation: The Pre-Check checks to see if the Inventory Service is running. If not, it reports a fatal error and stops. Resolution: You can try manually starting the inventory service and re-trying the Pre-Check. If it still fails, contact support. Message: ERROR:System Status Monitor registry key is corrupt or missing. Cannot continue validation. Explanation: The System Status Monitor registry key is required for Pre-Check to function. If it's missing or can't be read, we can't continue validation and so report a fatal error. Resolution: Contact support. Message: FAIL: Could not determine computername from registry Explanation: Pre-Check attempts to read the computer name from the registry. If it can't, it reports a failure. Resolution: Log into the BCM serial console, or use VNC. Ensure the computer name is in the BCM registry at key SYSTEM\CurrentControlSet\Control\ComputerName\ComputerName If not, call support, and do not add the name to the registry unless advised to do so by support. Message: ERROR:Could not run BIOSver to fetch versions. Explanation: Pre-Check run BIOSver.exe to fetch the motherboard version, product version (BCM200/400/1000) and the BIOS version. If it fails to run, Pre-Check cannot determine the product and so it reports a fatal error and stops. Resolution: Try rebooting the BCM and waiting 15 minutes, then running the Pre-Check tool again. If you still get the same issue, contact support to determine if you have the latest version of the Pre-Check tool and to obtain further direction. Message: ERROR:BIOSver did not produce output, cannot fetch versions Explanation: Pre-Check did run BIOSVer.exe successfully, but BIOSVer.exe didn't produce any output. In this case, Pre-Check cannot determine the product so reports a fatal error and stops. Resolution: Try rebooting the BCM and waiting 15 minutes, then running the Pre-Check tool again. If you still get the same issue, contact support to determine if you have the latest version of the Pre-Check tool and to obtain further direction. Message: ERROR:Motherboard version could not be determined. Explanation: The output from BIOSVer.exe could not be parsed to determine the motherboard version, so Pre-Check reports a fatal error and stops. Resolution: Try rebooting the BCM and waiting 15 minutes, then running the Pre-Check tool again. If you still get the same issue, fetch the file C:\Upgrade\logs\BIOSver.out from the BCM and contact support. Message: ERROR:Could not determine product version. Explanation: The output from BIOSVer.exe could not be parsed to determine the product version, so Pre-Check reports a fatal error and stops. Resolution: Same as for ERROR:Motherboard version could not be determined. Message: ERROR:BIOS version could not be determined. Explanation: The output from BIOSVer.exe could not be parsed to determine the BIOS version, so Pre-Check reports a fatal error and stops. Resolution: Same as for ERROR:Motherboard version could not be determined. Message: FAIL: No drive C:, or drive label is not WINNT, or drive is not NTFS Explanation: Pre-Check checks that the C: drive exists, is labeled WINNT and is file system NTFS. If not, Pre-Check reports a failure. Resolution: The resolution for all partitioning issues is the same: - Backup the BCM - Re-image the BCM to the correct version (3.6/3.7) using the BIT tool - Restore the backup - Try the Pre-Check again If the Pre-Check still fails, fetch the file c:\Upgrade\logs\chkPtns.out from the BCM and contact support. Message: FAIL: Could not determine the partition for the C: drive Explanation: If Pre-Check fails to determine the partition the C: drive is on, it reports a failure. Resolution: See standard partitioning issue resolution under FAIL: No drive C: Message: FAIL: C: must be partition 1 or 2 on BCM1000 Message: FAIL: C: must be partition 2 on BCM200 Message: FAIL: C: must be partition 2 on BCM400 Explanation: For BCM1000 units, Pre-Check reports a failure if the C: drive is not found on partition 1 or 2. For BCM200 and BCM400 units, Pre-Check reports a failure if the C: drive is not found on partition 2. Resolution: See standard partitioning issue resolution under FAIL: No drive C: Message: FAIL: No drive D:, or drive label is not DATA, or drive is not NTFS Explanation: Pre-Check checks that the D: drive exists, is labeled DATA and is file system NTFS. If not, Pre-Check reports a failure. Resolution: See standard partitioning issue resolution under FAIL: No drive C: Message: FAIL: No drive E:, or drive label is not LOGS, or drive is not NTFS Explanation: Pre-Check checks that the E: drive exists, is labeled LOGS and is file system NTFS. If not, Pre-Check reports a failure. Resolution: See standard partitioning issue resolution under FAIL: No drive C: Message: FAIL: No drive F:, or drive label is not NNACTIVE/NNINACTIVE, or drive is not NTFS Explanation: Pre-Check checks that the F: drive exists, is labeled NNACTIVE or NNINACTIVE, is file system NTFS. If not, Pre-Check reports a failure. Resolution: See standard partitioning issue resolution under FAIL: No drive C: Message: FAIL: No drive G:, or drive label is not NNACTIVE/NNINACTIVE, or drive is not NTFS Explanation: Pre-Check checks that the G: drive exists, is labeled NNACTIVE or NNINACTIVE, is file system NTFS. If not, Pre-Check reports a failure. Resolution: See standard partitioning issue resolution under FAIL: No drive C: Message: FAIL: Drive with label MAINTOS must be I: on BCM200 and BCM400 and must be type NTFS Message: FAIL: Drive with label MAINTOS must be H: or I: on BCM1000 and must be type NTFS Explanation: On BCM200 and BCM400, MAINTOS must be I: and type NTFS. On BCM1000, MAINTOS must be H: or I: and type NTFS. Resolution: See standard partitioning issue resolution under FAIL: No drive C: Message: FAIL: H: drive is label MAINTOS, and is not on partition 1 Message: FAIL: H: drive must exist on partition 1 for BCM 200/400 Explanation: There must be an H: drive on partition 1 for BCM200 and BCM400. For BCM1000, if there is an H: drive, and it's not MAINTOS, it must be on partition 1. Resolution: See standard partitioning issue resolution under FAIL: No drive C: Message: FAIL: Missing volume name DATA Message: FAIL: Missing volume name LOGS Message: FAIL: Missing volume name NNACTIVE Message: FAIL: Missing volume name NNINACTIVE Message: FAIL: Missing volume name WINNT Message: FAIL: Missing volume name MAINTOS Explanation: Drive labels DATA, LOGS, NNACTIVE, NNINACTIVE, WINNT and MAINTOS must exist. Resolution: See standard partitioning issue resolution under FAIL: No drive C: Message: FAIL: Volume LOGS must be on extended partition Message: FAIL: Volume NNACTIVE must be on extended partition Message: FAIL: Volume NNINACTIVE must be on extended partition Explanation: Volumes LOGS, NNACTIVE and NNINACTIVE must be on the extended partition, and may not be on a primary partition. Resolution: See standard partitioning issue resolution under FAIL: No drive C: Message: FAIL: Volume WINNT must not be on extended partition Message: FAIL: Volume MAINTOS must not be on extended partition Explanation: Volumes WINNT and MAINTOS must not be on the extended partition, but instead are expected to be on primary partitions. Resolution: See standard partitioning issue resolution under FAIL: No drive C: Message: FAIL: Could not determine the drive letter for the primary partition Explanation: The Pre-Check tool could not determine the drive letter for the primary partition. Resolution: Reboot the BCM and try again. If the Pre-Check still fails, see standard partitioning issue resolution under FAIL: No drive C: Message: FAIL: The primary partition must be either C: or H:, but is %DRV_INITPART% Explanation: The primary partition must be either drive C:, or drive H:, but it is not. Resolution: See standard partitioning issue resolution under FAIL: No drive C: Message: FAIL: Could not find DriveQuery executable Explanation: If DriveQuery.log does not exist, Pre-Check runs DriveQuery.exe to generate it to determine information about drive partitioning. If DriveQuery.exe doesn't exist, Pre-Check cannot generate the drive query report, so it reports a fatal error and stops. Resolution: This is usually a problem with the Pre-Check tool missing the DriveQuery.exe file, but it can also be caused by the file not being copied to the BCM correctly. Re-extract the self-extracting executable (distribution) and re-try the Pre-Check. If it fails again, contact support. Message: FAIL: Could not find DriveQuery log file C:\Upgrade\logs\DriveQuery.log Explanation: If DriveQuery.log does not exist, Pre-Check runs DriveQuery.exe to generate it to determine information about drive partitioning. If C:\Upgrade\logs\DriveQuery.log is not generated, Pre-Check cannot determine the partitioning information it needs, so it reports a fatal error and stops. Resolution: Try rebooting the BCM and attempting the Pre-Check again. If it fails again, contact support. Resolution: See standard partitioning issue resolution under FAIL: No drive C: Message: FAIL: Could not parse drive C: from DriveQuery output Message: FAIL: Could not parse drive D: from DriveQuery output Message: FAIL: Could not parse drive E: from DriveQuery output Message: FAIL: Could not parse drive F: from DriveQuery output Message: FAIL: Could not parse drive G: from DriveQuery output Message: FAIL: Could not parse MAINTOS drive H: from DriveQuery output Message: FAIL: Could not parse MAINTOS drive I: from DriveQuery output Explanation: Pre-Check was unable to parse C:\Upgrade\logs\DriveQuery.log to determine the partitioning information it needed for the indicated drive. Resolution: See standard partitioning issue resolution under FAIL: No drive C: Message: FAIL: Expected H: partition to appear before D: partition Message: FAIL: Expected H: partition to appear before C: partition Message: FAIL: MAINTOS I: partition does not appear before D: partition Message: FAIL: C: partition should appear before D: partition Message: FAIL: D: partition should appear before E: partition Message: FAIL: D: partition should appear before F: partition Message: FAIL: D: partition should appear before G: partition Explanation: Pre-Check checks the ordering of the partitions expecting the following: C: partition must appear before D: partition. D: partition must appear before E:, F:, and G: partitions. If H: partition exists and is MAINTOS, then it must appear before the D: partition. If H: partition exists and is NOT MAINTOS, then it must appear before the C: partition. If I: is MAINTOS, then I: partition must appear before D: partition. If any of these tests fail, Pre-Check reports it. Resolution: See standard partitioning issue resolution under FAIL: No drive C: Message: FAIL: C: partition on BCM200/400 must be 2,623,863,808 bytes Message: FAIL: Could not determine size of drive C: Message: FAIL: C: partition on BCM1000 must be at least 2,623,863,808 bytes Message: FAIL: D: partition on BCM200/400 must be 9,911,427,072 bytes Message: FAIL: Could not determine size of drive D: Message: FAIL: D: partition on BCM1000 must be at least 9,911,427,072 bytes Message: FAIL: E: partition must be 2,105,638,912 bytes Message: FAIL: F: partition must be 2,105,638,912 bytes Message: FAIL: G: partition must be 2,105,638,912 bytes Message: FAIL: MAINTOS partition on BCM200/400 must be 1,052,835,328 bytes Message: FAIL: Could not determine size of MAINTOS drive Message: FAIL: MAINTOS partition on BCM1000 must be at least 1,052,834,816 bytes Explanation: Pre-Check checks the sizes of the partitions expecting the following: If system is BCM200/400: C: must be 2,623,863,808 bytes. D: must be 9,911,427,072 bytes. I: must be 1,052,835,328 bytes. If system is BCM1000, C:, D: and I: drives may be formatted as above, but if not must respect the following: C: must be at least 2,623,863,808 bytes. D: must be at least 9,911,427,072 bytes. I: or H: must be label MAINTOS and at least 1,052,834,816 bytes. If any of these tests fail, Pre-Check reports it. Resolution: See standard partitioning issue resolution under FAIL: No drive C: Message: FAIL: Service voicemscdriver 1 is missing Message: FAIL: Service voicemscservice 1 is missing Message: FAIL: Service VoiceCTI 1 is missing Message: FAIL: Service cfsServer 1 is missing Message: FAIL: Service VoiceMail 1 is missing Message: FAIL: Service EmsManager 1 is missing Message: FAIL: Service Router 1 is missing Message: FAIL: Service MGS 1 is missing Message: FAIL: Service MPS 1 is missing Message: FAIL: Service UTPS 1 is missing Message: FAIL: Service winvnc 1 is missing Message: FAIL: Service VoiceRecord 1 is missing Message: FAIL: Service voicewatchdog 1 is missing Message: FAIL: Service VoiceNetQosMonitor 1 is missing Explanation: Pre-Check expects the services voicemscdriver, voicemscservice, VoiceCTI, cfsServer, VoiceMail, EmsManager, Router, MGS, MPS, UTPS, winvnc, VoiceRecord, voicewatchdog and VoiceNetQosMonitor to exist. They don't have to be running, but they must exist. If any of the listed services does not exist on the BCM, it is reported as a failure. Resolution: Try rebooting the BCM and attempting the Pre-Check again. If it fails again, contact support. Message: ERROR:BCM Version check. BCM version %bcmVersion% build %bcmBuild% is NOT supported for this upgrade Explanation: Pre-Check checks the BCM version and build. If the BCM is not version 3.6 Build 2.2c, version 3.6 Build 3.1a or BCM 3.7 Build 2.4f, it reports a fatal error and stops. Resolution: There is no resolution to this issue as only the documented versions of BCM are supported. Message: FAIL: Computername: %ComputerName%. (Which will be followed by one or more of the following three conditions) Computername must be between 1 and 24 characters. Computername must not start with dash character. Computername must consist only of alphanumeric characters and may also include dash characters. Explanation: The computer name must confirm to the following rules: - The computer name cannot be blank. - The computer name cannot be greater than 24 chars in length. - The only valid characters for the computer name are upper and lower case alphabetic characters (A-Z), numeric characters (0-9), and the dash character ("-"). - Notwithstanding the acceptable character list above, the first character of the computer name may not be the dash character ("-"). Resolution: Change the BCM name to conform to the rules and try the Pre-Check again. Message: FAIL: Disk size check. Disk is %ntotalDiskSize% GB. Only 20 GB drives are supported by this upgrade Explanation: The size of the BCM hard drive is checked to be sure it falls within a certain range, centered around 20 gigabytes. If the drive size does not fall within this range, the failure message above is produced. Resolution: Check that the hard drive is one of the supported models for BCM 3.X. If it is, not, call support. If it is, try the Pre-Check again and if it still reports failure, call support. Message: FAIL: BCM drive C: check. Drive C: does NOT have sufficient space Explanation: The C: drive is checked to see if it has a minimum of 140 megabytes of free space. If it does not, the above failure message is reported. Resolution: You will need to remove any unneeded files from drive C: and try the Pre-Check again. Message: FAIL: BCM drive D: check. Drive D: does NOT have sufficient space Explanation: The D: drive is checked to see if it has a minimum of 300 megabytes of free space. If it does not, the above failure message is reported. Resolution: You will need to remove any unneeded files from drive D: and try the Pre-Check again. Because the D: drive is the DATA drive, removing some voice mail messages is usually the easiest way to free up space on the D: drive. Message: FAIL: BCM drive E: check. Drive E: does NOT have sufficient space Explanation: The E: drive is checked to see if it has a minimum of 200 megabytes of free space. If it does not, the above failure message is reported. Resolution: You will need to remove any unneeded files from drive E: and try the Pre-Check again. Message: FAIL: Extended partition offset check. Could not find extended partition Explanation: There are should be three primary partitions, and one extended partition on the BCM 3.X. If the extended partition could not be found, the above failure message is reported. start at at least a particular offset. If it starts at an earlier offset, it is reported as a failure. Resolution: See standard partitioning issue resolution under FAIL: No drive C: Message: FAIL: Extended partition check. Extended partition must start at at least offset 106928640 and is currently set to start at %startingOffset% Explanation: There are should be three primary partitions, and one extended partition on the BCM 3.X. The extended partition is expected to start at least a particular offset. If it starts at an earlier offset, it is reported as a failure. Resolution: See standard partitioning issue resolution under FAIL: No drive C: Message: FAIL: Voice Mail and IVR check. Could not open D:\Data Files\Nortel Networks\Voice CTI\FILEPOOL so cannot determine Voice Mail and IVR storage limits. Explanation: In order to determine if the Voice Mail and IVR files exceed the maximum that can be preserved for Upgrade, Pre-Check needs to open the folder D:\Data Files\Nortel Networks\Voice CTI\FILEPOOL. If that folder cannot be found or opened, the above failure message will be displayed. Resolution: Verify that the folder D:\Data Files\Nortel Networks\Voice CTI\FILEPOOL\ exists on the BCM and can be opened. If not, reboot the BCM and try the Pre-Check again. If the problem is reported again, call support. Message: FAIL: Voice Mail and IVR check. Existing Voice Mail and IVR storage exceeds 200 hours Explanation: Upgrade can only preserve up to 200 hours of Voice Mail and IVR and will report a failure if it detects that this limit is exceeded. Note that this limit includes some of the voice language prompts. Resolution: Have the users or the operator delete unneeded Voice Mail messages. Also, the operator may delete any unneeded IVR files. Try the Pre-Check again. If it still reports the storage exceeds 200 hours, you will need to delete more Voice Mail and/or IVR files. If you feel that you are getting this message in error, i.e., if you have reason to believe the Voice Mail and IVR, plus the language prompts do not exceed 200 hours, please contact support. Message: FAIL: IP Music check. Could not open D:\Data Files\Nortel Networks\BcmAmp\AudioData so cannot determine IP Music storage limits Explanation: In order to determine if the IP Music files exceed the maximum that can be preserved for Upgrade, Pre-Check needs to open the folder D:\Data Files\Nortel Networks\BcmAmp\AudioData. If that folder cannot be found or opened, the above failure message will be displayed. Resolution: Verify that the folder D:\Data Files\Nortel Networks\BcmAmp\AudioData\ exists on the BCM and can be opened. If not, reboot the BCM and try the Pre-Check again. If the problem is reported again, call support. Message: FAIL: IP Music check. Existing IP Music storage exceeds 300 megabytes Explanation: Upgrade can only preserve up to 300 megabytes of IP Music files and will report a failure if it detects that this limit is exceeded. Resolution: The operator should delete any unneeded IP Music files and try the Pre-Check again. If it still reports the IP Music storage exceeds 300 megabytes, you will need to delete more IP Music files. If you feel that you are getting this message in error, i.e., if you have reason to believe the IP Music files total 300 megabytes or less, please contact support. Message: FAIL: Call Detail Recording check. Could not open D:\Data Files\Nortel Networks\Call Detail Recording so cannot determine Call Detail Recording storage limits Explanation: In order to determine if the Call Detail Recording files exceed the maximum that can be preserved for Upgrade, Pre-Check needs to open the folder D:\Data Files\Nortel Networks\Call Detail Recording. If that folder cannot be found or opened, the above failure message will be displayed. Resolution: Verify that the folder D:\Data Files\Nortel Networks\Call Detail Recording\ exists on the BCM and can be opened. If not, reboot the BCM and try the Pre-Check again. If the problem is reported again, call support. Message: FAIL: Call Detail Recording check. Existing Call Detail Recording storage exceeds 200 megabytes Explanation: Upgrade can only preserve up to 200 megabytes of Call Detail Recording files and will report a failure if it detects that this limit is exceeded. Resolution: The operator should delete any unneeded Call Detail Recording files and try the Pre-Check again. If it still reports the Call Detail Recording storage exceeds 200 megabytes, you will need to delete more Call Detail Recording files. If you feel that you are getting this message in error, i.e., if you have reason to believe the Call Detail Recording files total 200 megabytes or less, please contact support. Message: FAIL: HardDrive model check. Upgrade does not support RAID systems Explanation: Pre-Check has detected that there is a RAID system installed on the BCM. Upgrade does not support RAID systems. Resolution: Please contact support. Message: FAIL: HardDrive model check. HardDrive model is unknown Explanation: Pre-Check was unable to determine the hard drive model in the BCM. Resolution: Reboot the BCM and try the Pre-Check again. If it reports the same issue, please contact support. Message: ERROR:Couldn't find strings.exe so cannot parse inventory Explanation: Pre-Check needs to be able to run the tool strings.exe against the inventory.xml file in order to prepare it for processing but for some reason it was unable to find the strings.exe tool. Without the ability to process inventory.xml, Pre-Check is unable to proceed, so it reports a fatal error and stops. Resolution: Reboot the BCM and try the Pre-Check again. If it reports the same issue, please contact support. Message: ERROR: There was a problem refreshing the system inventory. Be sure the inventory service is running Explanation: Pre-Check needs to be able to regenerate the inventory.xml file to determine details about the BCMs hardware. In order to do this the inventory service needs to be present and running. If it is not, Pre-Check is unable to proceed, so it reports a fatal error and stops. Resolution: Ensure that the inventory service is running on the BCM. If it is not, start it, or reboot the BCM and try the Pre-Check again. If it reports the same issue, please contact support. Message: ERROR: There was a problem generating the system inventory file. Be sure the inventory service is running and the file F:\Program Files\Nortel Networks\Voice Platform\wwwroot\inventory.xml exists Explanation: Pre-Check calls code to regenerate the inventory.xml file (which it uses to determine details about the BCMs hardware) and it then waits a while until inventory file exists. Pre-Check tests for the file 6 times, waiting 10 seconds between checks. Note, we are not checking to see that the file is fully generated, just that the generation has started. If after 6 tries the inventory.xml file still does not exist, Pre-Check is unable to proceed, so it reports a fatal error and stops. Resolution: Reboot the BCM and try the Pre-Check again. If it reports the same issue, please contact support. Message: ERROR: Problem running strings.exe. Return value is %nReturn% Explanation: Pre-Check needs to be able to run the tool strings.exe against the inventory.xml file in order to prepare it for processing but for some reason it was unable to run the strings.exe tool. Without the ability to process inventory.xml, Pre-Check is unable to proceed, so it reports a fatal error and stops. Resolution: Reboot the BCM and try the Pre-Check again. If it reports the same issue, please contact support. Message: ERROR: System inventory file was only partially re-generated. Be sure the inventory service is running, the file F:\Program Files\Nortel Networks\Voice Platform\wwwroot\inventory.xml exists and the file contains the text Explanation: To be sure the inventory file is fully generated, we check it for the tag "". If the tag is not found, we sleep 10 seconds, and check again. We do this up to 60 times. It generally takes up to 30s, but we have found that on BCM200/400 with PIII 700Mhz chips, it can take longer than 6 minutes. If after 60 tries the inventory.xml file still does not exist, Pre-Check is unable to proceed, so it reports a fatal error and stops. Resolution: Reboot the BCM and try the Pre-Check again. If it reports the same issue, please contact support. Message: FAIL: MSC Card check. MSC card is not a supported type. Expected MSC1A but the value read was [ %MSCVersion% ] Explanation: Only MSC1A cards or cards that report as MSC1A are supported for Upgrade. Pre-Check will report a failure if it does not detect an MSC1A card. Resolution: Reboot the BCM and try the Pre-Check again. If it reports the same issue, please contact support. Message: FAIL: MSC check. KSU version (MSC Core) is [ %coreVersion% ] which is NOT supported. Explanation: Pre-Check determines the core version, which is usually a string of the form 30DeG04. It inspects the 3rd and 4th characters, in our example that would be "De". The table shows the supported core versions for BCM 3.6 and BCM 3.7, and the human readable name the versions are known by: 3.6 3.7 Name --- --- --------- Da Dg CT2Plus Db Dh E1Cala Dc Di Etiquette Dd Dj E1 De Dk E1Gl If the core version is not shown in the table, or does not match the BCM version, Pre-Check will report it as a failure. Resolution: Re-initialize the BCM to upload the MSC core (this will take a long time, usually in excess of 15 minutes). Reboot the BCM and try the Pre-Check again. If it reports the same issue, please contact support. Message: FAIL: Check PECs. RunChkEl.bat did not run or chkel.txt not generated. Unable to check PECs Explanation: In order to gather information about the PECs, Pre-Check needs to run the script RunChkEl.bat which generates the file chkel.txt. If it cannot run RunChkEl.bat or the file chkel.txt does not get generated, Pre-Check cannot determine PEC information, and so reports a failure. Resolution: Reboot the BCM and try the Pre-Check again. If it reports the same issue, please contact support. Message: FAIL: Check PECs. The BCM has a problem with the MS-PECs Explanation: Pre-Check cannot determine the status of the PECS, so it reports the above failure. Resolution: Reboot the BCM and try the Pre-Check again. If it reports the same issue, please contact support. Message: FAIL: Check PECs. Zero PECs detected. Either bad PECs exists on the MSC card, the MSC card is not working properly or an unsupported configuration has been installed Explanation: Pre-Check has determined there are no PECs installed on the MSC card and so reports the above failure. Resolution: Ensure the correct number of PECs are installed on the BCM. Reboot the BCM and try the Pre-Check again. If it reports the same issue, please contact support. Message: FAIL: Check PECs. Three PECs detected Explanation: Pre-Check has determined there are three PECs installed on the MSC card which is an invalid configuration and so reports the above failure. Resolution: Ensure the correct number of PECs are installed on the BCM. Reboot the BCM and try the Pre-Check again. If it reports the same issue, please contact support. Message: FAIL: RAM check. BCM has %nPhysicalMemory% megabytes of RAM. A minimum of 250M is required Explanation: Pre-Check determines the amount of RAM installed on the BCM and if it does not meet the minimum requirements, reports the above failure. Resolution: Ensure there is at least 250 megabytes of RAM installed on the BCM. Reboot the BCM and try the Pre-Check again. If it reports the same issue, please contact support. Message: FAIL: European market profile detected. This market profile is unsupported in Business Communications Manager 3.7. All MSC Telephony programming will be lost and must be reconfigured after the upgrade Explanation: Self explanatory. Resolution: Ensure that European market profile is not selected. Reboot the BCM and try the Pre-Check again. If it reports the same issue, please contact support. Message: FAIL: Date check. The system date must be configured correctly before the BCM 4.0 Upgrade will proceed. Explanation: If the BCM date is before January 1, 2003, then the date is not configured correctly and the above failure will be reported. Resolution: Correct the date setting on the BCM, reboot it and try the Pre-Check again. If it reports the same issue, please contact support. Message: FAIL: precheck.vbs did not run, report is incomplete Explanation: One of the Pre-Check scripts did not run so the report will be incomplete. Resolution: Reboot the BCM and try the Pre-Check again. If it reports the same issue, please contact support. Message: FAIL: precheck.vbs is still running, report is incomplete Explanation: One of the Pre-Check scripts is still executing but is not expected to be. The report will be incomplete. Resolution: Reboot the BCM and try the Pre-Check again. If it reports the same issue, please contact support.