Jump to content
Welcome to our new Citrix community!

NS 11.0 build 62-10 - STA (FQDN) appears DOWN - Bug?


Recommended Posts

Not sure if anyone else is seen this before on NetScaler Firmware build 11.0 62_10

 

Issue:

 

NetScaler Gateway STA appears to be DOWN when a FQDN is being supplied and it only works if we supply an IP address. Note:  The diagnostics have been run (nstcpdump and dns looks (host, ping)) and it seems successful. i.e. NetScaler can actually resolve the FQDN and ports are reachable as well but from the "add STA Wizard" it simply doesn't work!!

 

 

Bug maybe? has anyone encountered this before? 

 

 

cheers

Vinay

Link to comment
Share on other sites

Odd one this...  I've got a single hop implementation and STA's run on standard port (80).  

 

Update

Added the second STA server with FQDN and works absolutely fine! I've ruled out DNS issues and Network connectivity (TCPDUMPs successful syn-acks).

 

On a development build of NetScaler running the latest firmware and identical setup - I'm able to add the first STA server with FQDN and status is absolutely fine!!? Not sure why i'm only experiencing this with the production pair.

 

I've scheduled a reboot - will let you know how it goes. On a side note, we do use GSLB with split-brain and quirky DNS Views that works a treat. But not sure if these affect the standard DNS resolution of non-GSLB services.

 

Diagnostics below (from Production NetScaler to STA in question)

 

root@MPL-NS01# nstcpdump.sh -c 10 -nn host 172.XX.XX.4
reading from file -, link-type EN10MB (Ethernet)
09:56:54.192616 IP 172.XX.XX.100.35995 > 172.XX.XX.4.80: Flags , seq 1530131242, win 8188, options [mss 1460], length 0
09:56:54.193017 IP 172.XX.XX.4.80 > 172.XX.XX.100.35995: Flags [s.], seq 3726813426, ack 1530131243, win 8192, options [mss 1460], length 0
09:56:54.193019 IP 172.XX.XX.100.35995 > 172.XX.XX.4.80: Flags [F.], seq 1, ack 1, win 8188, length 0
09:56:54.193203 IP 172.XX.XX.4.80 > 172.XX.XX.100.35995: Flags [.], ack 2, win 64240, length 0
09:56:54.193732 IP 172.XX.XX.4.80 > 172.XX.XX.100.35995: Flags [F.], seq 1, ack 2, win 64240, length 0
09:56:54.193733 IP 172.XX.XX.100.35995 > 172.XX.XX.4.80: Flags [.], ack 2, win 8188, length 0
 
 
 
root@MPL-NS01# host sta01.example.org.uk
sta01.example.org.uk has address 172.XX.XX.4

 

cheers

Vinay

Link to comment
Share on other sites

  • 4 months later...

Hi Vinay,

 

I am seeing similar issue in production.

NS version: NS 11, 62.10nc

I have 2 STA, both has been configured with FQDN. One shows UP another shows DOWN

Both are in same subnet x.x.x.15/x.x.x.16

If I configure STA with IP address, it shows UP

I have verified DNS and Reachability from NS to STA all seems to be fine. DNS Name Server is UP in NS

 

Question: What is the status of your problem ? Is this a bug ?

 

Thanks, 

Saifee Hussain

Link to comment
Share on other sites

  • 2 weeks later...
  • 2 weeks later...

Same issue here, running Netscaler 11.0 build 63.16.  STAs show down when entered with FQDN, but are up when entered via IP.  DNS resolution to same servers works fine everywhere else except for STA.  Adding static DNS records on the Netscaler does not resolve the issue.

 

Worth noting, issue started immediately after upgrading delivery controllers from 7.5 to 7.6 FP3.  Prior to upgrade, STA worked fine via FQDN.

Link to comment
Share on other sites

Hi Saifee,

 

I'd to upgrade to NS 11.0 64.34 to get rid of this problem. What platform are your experiencing this on btw? i.e. MPX, VPX

 

cheers

Vinay

Its VPX and it was working fine with FQDN before but as Richard said, there was a upgrade of XD as well in my environment. Yups agree could be a bug.

Link to comment
Share on other sites

  • 5 months later...
  • 3 months later...

Seeing issues here with multiple clients, on different versions of 11.x

 

Specifically

11.0 Build 62.10

11.0 Build 63.16

11.0 Build 64.34

 

After an HA failover, or restart of a device, all FQDN STAs will show down. The NetScaler is able to resolve the FQDN and can ping and telnet to it successfully.

 

After swapping the STAs from FQDN to IP Addresses, they will show up immediately (same STA #)

  • Like 1
Link to comment
Share on other sites

  • 2 months later...

Same issue here, running Netscaler 11.0 build 63.16.  STAs show down when entered with FQDN, but are up when entered via IP.  DNS resolution to same servers works fine everywhere else except for STA.  Adding static DNS records on the Netscaler does not resolve the issue.

 

Worth noting, issue started immediately after upgrading delivery controllers from 7.5 to 7.6 FP3.  Prior to upgrade, STA worked fine via FQDN.

 

Same issue here. Same NS build. We were already on 7.6 FP3. All we did was an HA fail over and the problem presented itself. 

Link to comment
Share on other sites

  • 2 years later...

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...