My Oracle Support Banner

ECE Clustered Target Hostname Issue (Doc ID 2375335.1)

Last updated on MARCH 29, 2018

Applies to:

Application Management Pack for Oracle Communications - Version 13.1.1.1.0 and later
Information in this document applies to any platform.

Symptoms

On :  13.1.1.1.0 version, ECE Plug-in

Scenario
---------------
User has requirement to monitor ECE cluster having nodes from different machines and is able to discover this clustered ECE setup. However the hostname and the name of the nodes are coming wrong. The host from which the target discovery is triggered, that particular hostname is getting populated instead of the actual one. For example, you have two machines vvssxxx51, vvssxx31. EMGateWay node belongs to vvssxx31 machine. When target discovery is triggered from vvssxx51 machine, the EmGateway node is getting the hostname as "vvssxxx51" instead of the actual one which is "vvsxxx31". Also the name of the node is being set wrongly as "vvssxxx51.xxxx:emGateway1".

EXPECTED BEHAVIOR
-----------------------
Since EMGateWay node belongs to vvssxxx31 machine. Expected see the home name with vvssxxx31 and correct name of node.



Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.