Jump to content
Welcome to our new Citrix community!

Citrix ADM Service no Virtual Servers are seen for license and Analytics under "All Virtual Servers" tab and Analytics config can't be applied.


Recommended Posts

Hello,

 

I am playing around with the Citrix ADM service Express acount and an unlicensed VPX (Freemium free license version 13.1-24.38) on my Vmware workstation. The first issue I saw that after the ADM discovered my VPX using the built-in agent there were no virtual servers under "All Virtuial Servers", so that I can use my 2 trial licenses for licensing the VS for Analytics. I worked around by creating an application that seemed to trigger discovery and all 3 servers were there seen.  I tried to trigger Rediscover of the ADC Instance but I saw this error "Invalid POST request, payload should start with object=" so creating an Application seems the only workaround for now maybe try to remove or add the VPX ADC instance or move it to Unmanage then Manage could help but will see about that ?

 

image.png

 

 

 

Now the second issue is that when I license and try to apply the Analytics config I see the following error :

 

image.thumb.png.a73e209b687886f298c673729bb8f983.png

 

 

image.thumb.png.2a7dbd4ff624f070c6ff419e501917cd.png

 

 

Just as a note I have not enabled any inbound connections from the Citrix ADM Cloud Service to my Citrix ADC built-in agent but most things seem to work as it seems the agent initiates the connections to the ADM service as I have no issue to push StyleBooks or Configuration Jobs, so should I enable any inbound connections from the Citrix Cloud on my home router to solve this issue or there is no need?

 

 

Link to comment
Share on other sites

I checked the Citrix VPX ns.log and saw that when using the ADM tries to create app_flow collector with ip address 127.0.0.1 it is not created as the IP address is shown as invalid. For some reason the ADM logs showed the app_flow policy not existing as an issue and not error seen in the VPX logs about the app_flow collector that is before that as it is normal that when the app_flow collector is not created then the app_flow action and after that the app_flow policy will not be created and will not exist ? . It seems an issue with the built-in agent on the Citrix ADC VPX as 127.0.0.1 just is not accepted. When I deployeed an ESXI agent on the Vmware and used it not the build-in one there were no issues as the app_flow collector IP address that will be configured on the VPX will be the external agent IP address.

 

 

There was another issue with the external agent that the nsaaad service does not start after the ADM uutomatically upgrades the agent  but removing and again adding the agent fixes this issue and the agent is already upgraded, so it will not be upgraded again. Now also the virtual server disovery works better than with the build-in agent.

  • Like 1
Link to comment
Share on other sites

  • 1 year later...

Just a quick follow-up on this post. Had the same issue and had no idea how to fix it. After some talk with Citrix technical support the features that you and I have been trying to enable is not supported useing the built-in agent

 

https://docs.netscaler.com/en-us/citrix-application-delivery-management-service/getting-started/initiate-built-in-agent.html

 

NetScaler ADM supports management and monitoring of NetScaler instances using built-in agents. However, the following features are not supported in the built-in agent:

  • Application dashboard
  • Web Insight
  • SSL insight
  • HDX insight
  • Gateway insight
  • Security insight
  • Advanced analytics
  • Pooled licensing
Link to comment
Share on other sites

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...