Incorrect interface used by Monitoring Points with dual-ended paths resulting in path errors
search cancel

Incorrect interface used by Monitoring Points with dual-ended paths resulting in path errors

book

Article ID: 410491

calendar_today

Updated On:

Products

AppNeta

Issue/Introduction

Some c50/r90 Monitoring Points (MPs) have an incorrect IP address and hostname. This causes a problem in the dual-ended path since the return path shows errors due to incorrect target.

For example, for a particular Path, the MP should have the following Hostname and IP address:

myCMP.company-domain.com
192.168.0.5

But instead, it has:

cmp-appneta-01
192.168.0.1/16

Environment

Appneta Container Monitoring Points (cmp)

Cause

In AppNeta there are two concepts: hostname (the hostname of the container in this case) and the AppNeta name (what it is named in AppNeta- by default the hostname but can be renamed), as per:

TechDocs : AppNeta : AppNeta Name and Hostname – c50-Docker Compose

For containers, the IP it gets is dependent on if it is set up with host networking or bridge networking. Given the 192.168.0.1/16 address, this indicates the container has been set up with bridge networking, as per:

TechDocs : AppNeta : Set Up the c50-Docker Compose

 

Resolution

Configure the MP with Host networking and that should allow it to get the proper address & hostname