08-22-2012 07:41 PM
I am trying to work out why a port is known and being checked as UDP by the ADX.
I tried to add come content checks, but an error is displayed:
cannot configure content-check-carray, port is bound to UDP port!
The VIP is showing port 104 as "FAL"
On the real-server I see UDP requests every 4 seconds?
12:38:57.563051 IP 172.25.68.88.1798 > 172.25.68.201.104: UDP, length 256
12:39:01.563278 IP 172.25.68.88.1797 > 172.25.68.201.104: UDP, length 256
12:39:05.563634 IP 172.25.68.88.1804 > 172.25.68.201.104: UDP, length 256
I need this port to be tcp-only as there is no LISTENER on the real server for UDP.
How can I determine why the ADX thinks its a UDP port?
Any help appreciated...Tks
server virtual viptest-CLI 172.25.68.225
port 104 sticky
port 104 tcp-only
port 104 lb-pri-servers backup-stay-active
bind 104 vipt1 104
server real vipt1 172.25.68.201
port default disable
port http keepalive
port http url "GET /index.html"
port 104 tcp-only
port 104 keepalive
hc-track-group 104 80
08-22-2012 08:35 PM
when port is unknown(not pre-defined), udp health check is performed by default. if you want tcp h/c, configure following.
server port 104
udp keepalive disable
Cli syntax will tell you what is known and unknown port. Also, slb guide(manual) will tell you.
i.e. server real and type port Tab key. you get following output. these are known application port.
DECIMAL Other well known application port number
disable-all Disable all the ports associated with this real server
unbind-all Unbind all the ports associated with this real server
08-22-2012 08:41 PM
I have also enclosed the guide to configure binary health checks for your reference.
08-22-2012 10:04 PM
I missed that bit
As port 104 (DICOM in my case) is not a known port it looking to health check via UDP.
So focused on trying to see where else in my config I had defined it as UDP....
Tks again. Checks are working great now and the track group is behaving as I expect.
Just some fine tuning on primary failbacks and I can put this to bed.