Bug ID 449793: Edge client doesn't use new Oesis SDK libraries unless it is restarted

Last Modified: Mar 12, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP APM(all modules)

Known Affected Versions:
10.1.0, 10.2.0, 10.2.1, 10.2.2, 10.2.3, 10.2.4, 11.0.0, 11.1.0, 11.2.0, 11.2.1, 11.3.0, 11.5.0, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9

Fixed In:
11.3.0 HF9, 11.2.1 HF11

Opened: Feb 21, 2014
Severity: 3-Major
Related AskF5 Article:
K17581

Symptoms

Edge client doesn't use new Oesis libraries unless it is restarted. When edge client starts, it updates Oesis libraries on the system if new version is found on BIG-IP, but it doesn't use those libraries unless it is restarted

Impact

Edge client uses old libraries of Oesis SDK. It might not leverage certain fixes made in new oesis SDK unless it is restarted

Conditions

BIG-IP Edge client and new EPSEC image on BIG-IP APM.

Workaround

Restart edge client after it updates the oesis libraries

Fix Information

Force restarting edge client when new epsec build is installed on BIG-IP.

Behavior Change