Layer7 API Management

Hi,

I have a two gateways cluster:

• 8.2 (ssg-8.2.01-1.noarch)
• Virtual Appliance
• 50 GB
• 2 GB RAM

I upgraded (using documentation and so on) the two nodes successfully to version 9.0, uploading and installing in this order next patches:

1. Layer7_PlatformUpdate_64bit_v8.3.00.L7P
2. Layer7_PlatformUpdate_64bit_v8.4.00.L7P
3. Layer7_PlatformUpdate_64bit_v9.0.00.L7P
4. Layer7_v9.0.00.L7P

The problem is that Primary Node doesn't display any change (the Seconday does). It still displays version 8.2 and doesn't allow me to upgrade the database. At the Patch Management Menu I can see that patches were successfully installed (corresponding files were created under /opt/SecureSpan/Controller/var/patches)

What could went wrong?

Thanks.

Best regards,

Andrés-J. Cremades

Hey Andres-J,

I have seen a few clients run into this kind of situation.  We were able to get around it by manually installing the rpms.

1) The L7P file is a zip archive. After copying the 9.0.00 Application L7P file to the /home/ssgconfig directory, the first step is to unzip the archive to a temporary directory;

# unzip -d /tmp/l7p /home/ssgconfig/Layer7_v9.0.00.L7P

2) Change to the directory containing the rpm files

# cd /tmp/l7p/com/l7tech/server/processcontroller/patching/builder/ResourcesPatchTask_1

3) Make certain the ssg service is stopped

# service ssg stop

4) Manually update the rpm files.

# /bin/rpm -Uvh ssg-9.0.00*.rpm ssg-appliance-9.0.00*.x86_64.rpm

5) Reboot the server

6) Check to see if the rpms are now correctly reflected as being 9.0.00

# rpm -qa | grep ssg

7) If all looks good then proceed to login to the ssgconfig menu and attempt

a database upgrade to 9.0.00

You might want to give this procedure a try and see if it gets you going.

Regards,

Daren

For the record of future community searches:

The issue was database upgrade through the ssgconfig menus.