Big news! The community will be moving to a new platform April 21. Read more.
Big news! The community will be moving to a new platform April 21. Read more.
Cadet 2nd Class Cadet 2nd Class
Cadet 2nd Class
485 views

AM 4.1: configure heartbeat url with ipadres instead of dns


In our loadbalancer we configured the heartbeat url to the NAM listen IP
addresses.
So the check the lb is doing is: http://ipadres/nesp/app/heartbeat

This gives us a bad request. That's clear because we need in the request
the published dns name.
But that's not easy for us because we have to configure a lot of probes
(every published dns name has is own IP address) in the lb.
If we can do this by IP address, we can create one generic probe.
Is there a way to do this?
(in the past, in our AM 3.1 we had this working, but I don't know how)


--
gschouten32
------------------------------------------------------------------------
gschouten32's Profile: https://forums.netiq.com/member.php?userid=2546
View this thread: https://forums.netiq.com/showthread.php?t=55672

0 Likes
5 Replies
Absent Member.
Absent Member.

gschouten32,

It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.

These forums are peer-to-peer, best effort, volunteer run and that if your issue
is urgent or not getting a response, you might try one of the following options:

- Visit http://www.netiq.com/support and search the knowledgebase and/or check
all the other self support options and support programs available.
- Open a service request: https://www.netiq.com/support
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.netiq.com)

Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.netiq.com/faq.php

Sometimes this automatic posting will alert someone that can respond.

If this is a reply to a duplicate posting or otherwise posted in error, please
ignore and accept our apologies and rest assured we will issue a stern reprimand
to our posting bot.

Good luck!

Your NetIQ Forums Team
http://forums.netiq.com


0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

gschouten32;2425143 wrote:
In our loadbalancer we configured the heartbeat url to the NAM listen IP
addresses.
So the check the lb is doing is: http://ipadres/nesp/app/heartbeat

This gives us a bad request. That's clear because we need in the request
the published dns name.
But that's not easy for us because we have to configure a lot of probes
(every published dns name has is own IP address) in the lb.
If we can do this by IP address, we can create one generic probe.
Is there a way to do this?
(in the past, in our AM 3.1 we had this working, but I don't know how)


--
gschouten32
------------------------------------------------------------------------
gschouten32's Profile: https://forums.netiq.com/member.php?userid=2546
View this thread: https://forums.netiq.com/showthread.php?t=55672


Which version of NAM are you on? There was a bug somewhere in one of the versions (I forget which) where the load balancer would check the IP, but NAM would whack the connect with a "bad response" (I forget the actual response), but it was caused by a bug.

We have a Cisco CSS set to use the IP, even though our AG Reverse proxy is setup by DNS, it still works.

We were able to dupe it fairly easily and get the error, I just don't remember what the actual response was though. But it caused our load balancer to mark the whole thing as down.

--Kevin
0 Likes
Cadet 2nd Class Cadet 2nd Class
Cadet 2nd Class


We are using 4.1 sp1 and are in an upgrade path to sp2. In the release
notes from sp2 I cannot find this issue.
It explains why this was working in our 3.1 environment.


--
gschouten32
------------------------------------------------------------------------
gschouten32's Profile: https://forums.netiq.com/member.php?userid=2546
View this thread: https://forums.netiq.com/showthread.php?t=55672

0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

gschouten32;2426093 wrote:
We are using 4.1 sp1 and are in an upgrade path to sp2. In the release
notes from sp2 I cannot find this issue.
It explains why this was working in our 3.1 environment.


--
gschouten32
------------------------------------------------------------------------
gschouten32's Profile: https://forums.netiq.com/member.php?userid=2546
View this thread: https://forums.netiq.com/showthread.php?t=55672


I think the bug was in 4.1.1
(I have a .zip file with 411 on it as a patch, so I think that's the bug) - checked my SR, yes bug is in 4.1.1
It's definitely resolved in 4.2 and 4.2 SP1

IF that's the bug

You'll see something in your AG apache error log file like:

httpd[7442]: [warn] AMEVENTID#628: ***Host Header Attack Detected, request is rejected*****, referer: http://10.10.106.22:81/nesp/app/heartbeat
0 Likes
Cadet 2nd Class Cadet 2nd Class
Cadet 2nd Class


thanks for suggestion, I'm going to check it out.


--
gschouten32
------------------------------------------------------------------------
gschouten32's Profile: https://forums.netiq.com/member.php?userid=2546
View this thread: https://forums.netiq.com/showthread.php?t=55672

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.