Last updated on MARCH 23, 2017
Applies to:Oracle Communications Session Monitor - Version 3.1.x and later
Information in this document applies to any platform.
This article is applicable for systems with Napatech card only as other systems may use a newer 3.2 or 3.16 kernels (for more information on versions and available kernels please see Doc ID 2081750.1 article - relevant is its first section, the explanation and not the actions noted in the KM). The reason is that an OCOM with Napatech card present needs to boot into the older 2.6 kernel that is present on any OCOM system and cannot use the 3.2/3.16.
Further, this article is applicable on the newer servers like a HP308 G9 as the older servers have better compatibility with the legacy 2.6 kernel.
The OCOM server needs a minimum of 8 CPU threads to run (or more - depending on the sizing of particular system). There is a know issue on some newer servers (like HP380 G9) with newer processors where the system does not recognize a multiple threads of the CPU (its cores or hyper-threading) and essentially OS has only one CPU thread available.
Since the system in such case runs with a single CPU thread (as opposed to 8+), it affects it performance severely and may lead to packet drops on the Napatech, processes restarts or general slowness of the GUI, delays on the data presence/retrieval.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms