NetScaler Built-in Agent Hello I have a problem with the Builtin agent and the NetScaler Console Service. The NS is correctly registered with NS Console Service but when I run the add licenceserver 127.0.0.1 -port 27000 I have got the error

Builtin agent doesn't support licensing.

I have a LSA Agent on another Datacenter

The config works at another site? I only know of the ability to point NS to a stand alone ADM Agent for licensing.

Yes

Ah, this is news to me. Sorry, I will be unable to assist. @Richard Faulkner ?

@Ryan Gallier: No problem, thank you for your help, really appreciated

I use this doc. It appaers that the agent was not present on one NS

ah, that's another thing to consider 👍

Sorry, pre-occupied today. The Built-in agent needs to be able to communicate both with the NetScaler Console Service and with the agent listed with the “LSA” marker. If communication is blocked, it won’t succeed.

No really agreed. From the documentation (and my experience) the Builtin Agent use the NS Console Service as a proxy to reach the LSA

I have seen instances where the NetScaler and the agent with the LSA could not communicate and it did not work. Not sure I could recreate it now.

As we see, the Mastools version is 0.0.0.0 on the netscaler that does not work. We don't understand why the Netscaler does not donwload the agent upgrade (this is the secondary but it works on another HA Pair). We will build a new one.

I have found HA pairs to be problematic as the standby device often loses communication. Please let me know how you fair with a different appliance.

Feel the same. Passive instance stays in grâce period. I have a this in the PTEC Slack. I hope to have an answer from the PM because Citrix does not mentioned that point in the docs.

Sounds good. I am interested in knowing the answer. I will gladly update the blog post.

I can only manage a NetScaler VPX through "NetScaler Console Service Agent" or "the built-in agent on the NetScaler", correct? Background: We already have a "NetScaler Console Service Agent" in-place, to orchestrate NetScaler Updates through NetScaler Console Service, but we don't allow any incoming traffic (27000 & 7279) and don't plan to. But I must switch licensing soon. Therefore my only options seem to be, to replace the current Service Agent, with a Service Agent, that allows incoming traffic. Or switch to the built-in agent and delete Service Agent.

You will need to have at least one Agent that can communicate on port 27000 and 7279 regardless. There must be an existing agent associated with the NetScaler Console Service that has the "LSA" role assigned for even the built-in agent to work. I believe the built-in agent communicates through the service through the agent paths, so 27000 ad 7279 should not be required outbound from a built-in agent.

Okay, we adjusted our architecture and now use the regular agent base licensing, not the built-in agent.

Also, you need at least one agent that can act as a Licensing Server Appliance (LSA); otherwise, you won't be able to apply your bandwidth and capacity licenses to ADM.

Is your route relying on a snip that is only present on the primary node rather than going out the management network? If it doesn’t work on the secondary I’d start there