Summary
Your beacon may fail to gather inventory from some Oracle VM Manager (OVMM) servers. This article describes a possible cause of this due to TLS configuration incompatibilities.
Cause
OVMM versions 3.4.5 and later can only communicate using TLS 1.2.
OVMM versions 3.4.4 and earlier can only communicate using TLS 1.0 and TLS 1.1.
FlexNet beacons cannot dynamically choose between TLS protocols based on the OVMM server versions.
Solution
If your OVMM servers are running version 3.4.5 or later you will need to configure your beacon to communicate over TLS 1.2. If TLS 1.0 and 1.1 are still enabled the communication wouldn't work correctly and inventory would fail.
If you have more than one version of OVMM on your environment you will have a situation where you have one or more servers that require communication using TLS 1.2, and other servers that require TLS 1.0 or 1.1 for communication. An approach here is to setup a two beacons:
- One beacon is configured to use TLS 1.2, and with OVMM inventory rules targeting OVMM servers running 3.4.5 and later.
- The other beacon is configured to use TLS 1.0 and 1.1, with inventory rules targeting OVMM servers running 3.4.4 and earlier.
With this setup your inventory for both environments should come in correctly.
See also
Transport Layer Security (TLS) 1.1 & 1.2 Configuration
