The following issues may be encountered during migration.
1. RedHat 5.5 x32 upgrade to RedHat 5.9 x32 on AMD.
RedHat 5.x prior 5.8 32-bit Server Edition upgrade to RedHat 5.9 (or newer) 32-bit Server Edition and AMD software upgrade from release prior 12.0.3 to release 12.2.
- RHEL 5.9 i386 (32-bit) Server Edition installation DVD
- 12.2.2 AMD upgrade.bin software
- Place RHEL 5.9 installation disk in dvd-rom drive
- Copy 12.2. AMD upgrade.bin to /root/ folder on AMD
- Stop the Agentless Monitoring Device. Use the following command: ndstop.
- Mount RHEL 5.9 installation DVD. Steps:
mkdir -p /var/www/html/cdrom/iso
mount -o loop /dev/cdrom /var/www/html/cdrom/iso
- Install createrepo and rpm (if not already installed) from the RedHat 5.9 DVD:
rpm -i iso/Server/createrepo-0.4.11-3.el5.noarch.rpm
rpm -i iso/Server/yum-3.2.22-40.el5.noarch.rpm
- Create local repository (this will take a few minutes to complete):
yum clean all
- Create a file /etc/yum.repos.d/file.repo which should have the following content:
[RHEL 5 Repository]
name=RH 5.9 Repo
- Create a file /etc/yum.repos.d/my.repo which should have the following content:
name=RHEL 5.9 Server Repository
- Remove tomcat-amd package
rpm -e --nodeps tomcat-amd
- Install tomcat5:
yum update tomcat5
press "Y" when prompted to "download" tomcat packages (download = served from local disk)
- Install new version of AMD code:
chmod 755 upgrade-amd-amdos5-i386-ndw-12-02-02-0085-b001.bin
Answer NO to this question (restart will be performed at the end of upgrade procedure):
System restart is required for the installation to take effect. Would you like to reboot now? (y/n) n
- Start RHEL OS upgrade:
Total download size: XXX M
Is this ok [y/N]: Y
- Remove RHEL 5.9 installation DVD from the drive
- Reboot system now
Upon first start the AMD will re-compile the custom drivers to the new kernel 2.6.18-348.el5PAE and this process takes a while (a few minutes)
- Verify if AMD functions properly:
a) run "ndstat" and make sure that all AMD processes listed are up and running
b) check if custom driver is used (if it was previously): rcon
"show status", check this section: Packet receiver status:
reading from dev: ethX, ethY, ethX
packets read: 77003, uses RTM custom network driver with packet copying) check if AMD produces zdata files in /var/spool/adlex/rtm/ folder
NOTE: Starting from release 12.4.1, RHEL 5 is not supported.
2. Upgrading CAS/ADS database takes hours.
The CAS/ADS software upgrade goes fairly fast, but when it gets to the step to upgrade the database, this lasts for several hours.
During a database upgrade, data is copied to temporary tables in order to perform data conversion. This procedure may require a significant amount of disk space and hence SQL server would need to allocate more disk space to the database files. Please note that the default value for Autogrowth in MBs is 10MB and if that was set during the database upgrade, SQL server will constantly try to allocate more disk space to increase the size of the database file and this causes the upgrade to slow done tremendously and take much longer to finish. It is suggested to increase the Autogrowth settings for the database files to 10% as it will scale better with the current size of the database and will allow SQL server to allocate disk space less frequently and this speeds up the upgrade process.
Note : Please note that NOT all slow upgrades are caused by low Autogrowth settings. Autogrowth settings should be checked prior to any upgrade to make sure this is not affecting the upgrade process. Slow upgrades could also be attributed to a slow or underpowered SQL server machine or simply a very large database.
Follow the below procedure in order to adjust the auto-growth setting on the database files to 10% of the file size:
- Go to SQL Management Studio.
- Expand Databases.
- Right-click the CAS or ADS database and click Properties.
- In the Database Properties dialog box, click Files.
- Under the Autogrowth column, click the "..." button next to the CAS or ADS logical file names:
6. Set the File Growth to 10%
7. Click OK to close all the dialog boxes and save the settings.
3. CAS doesn't process data after upgrading and restarting.
After upgrading CAS and restarting it, "Data Processing upper time limit is set" is reported without processing any data files until going to http://cas_IP_address/rtmdebug, and manually clicking "Unset_limit".
Open , choose Advanced Properties Editor, find the RtmJob.Step property and set it to OFF. Then restart the server - it should start processing data.
What to do next
Visit the DC RUM Migration Center to get migration guidelines and links to the most important resources.