Windows Client Deployments Can Cause GIM Server Disruption When 12.x Modules Are Used with Pre-12.x GIM Modules components

Flashes (Alerts)

Abstract

Under certain conditions, the GIM server can become unavailable due to incompatibilities between 12.x modules and pre-12.x GIM components. This issue may occur when 12.x GIM modules are uploaded to a pre-12.x appliance or when a 12.x.p100 Bundle S-TAP or FAM Monitor is installed while using a pre-12.x GIM client. Customers should review the conditions below and follow the recommended upgrade path to prevent disruption.

Content

The GIM server can become unstable or unavailable under either of the following conditions:

A pre-12.x appliance has 12.x GIM modules uploaded to it.
A 12.x.p100 Bundle S-TAP or FAM Monitor is installed while the Database server is using a pre-12.x GIM client.
In these scenarios, incompatible communication between GIM components may cause the GIM server to process malformed data, resulting in a disruption of GIM services. Because a single GIM server often manages multiple hosts, the impact can extend beyond the affected system and disrupt GIM communications for all the GIM clients connected to this GIM server.

12.x.p100 Windows GIM and STAP are removed from fix Central.

Workaround

There is no self-service workaround available.

Customers experiencing this issue should immediately contact IBM Support for assistance.

Resolution

Two independent prevention mechanisms have been implemented to eliminate this issue:

1. Client-Side Prevention (Windows GIM and S-TAP)

A preventive fix was introduced in 12.xp101 STAP and 12.xp101 GIM are available through IBM Fix Central.

2. Server-Side Prevention (GIM Server)

Additional protection was added on the appliance GIM server to prevent a single malformed client connection from disrupting all GIM client communications.

This server-side enhancement is included in:

Appliance Bundle 12.0 Q3
Guardium 12.1 September Fix Pack (targeted for end of September)
Appliance Bundle 12.1 Q3
Guardium 12.2.2 Fix Pack 12.0p1053. This patch is intended for 12.2.2 (p220) environments.
Guardium 12.2.3 August Fix Pack 12.0p233
Guardium 12.2.3 September Fix Pack (targeted for end of September)
GPU 12.2.4 (targeted for end of September)

Required Customer Action

Customers planning to deploy or upgrade to the 12.x release should ensure that all GIM infrastructure components are at compatible levels before installing 12.x.p101 Bundle S-TAP or FAM Monitor components.

Conditions That Can Trigger This Issue

A pre-12.x appliance has 12.x modules uploaded to it.
A 12.x.p100 Bundle S-TAP or FAM Monitor is freshly installed while using a pre-12.x GIM client.

Recommended Upgrade Order

Upgrade the GIM client to the 12.x release.
Verify successful GIM client connectivity.
Upgrade Bundle S-TAP or FAM Monitor components to the 12.x release.
Verify normal GIM communication after deployment.

[{"Type":"MASTER","Line of Business":{"code":"LOB76","label":"Data Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSMPHH","label":"IBM Security Guardium"},"ARM Category":[{"code":"a8m0z000000Gp0JAAS","label":"APPLIANCE"},{"code":"a8m0z000000Gp0IAAS","label":"STAP"}],"Platform":[{"code":"PF004","label":"Appliance"},{"code":"PF033","label":"Windows"}],"Version":"12.0.0;12.1.0;12.2.0"}]

Tips