not another las question... I have a problem with the buildin agent for LAS with 3 netscaler instances (14.1.60.67). When i launch ./mastools_init.sh <device_profile_name> <service_url> <activation_code> -profile i get this output and the instances do not appear on the Netscaler Console Service:

running image upgrade

Download site signature verification successful

Start downloadng image...

Download completed

Start upgrading...

Upgrade done

VPX registration with device profile provided

----------------------------------------------------------------------------

NetScaler Console Tools successfully registered.

----------------------------------------------------------------------------

14.1-68.30

re-registration, invoke the binary

MASTOOLS_PACKAGE_OS_VERSION: 8.4

MASTOOLS_CURRENT_OS_VERSION: 11.4

mastools package version and os version not match, clean up binary

Stopping mastools processes...

Using new method to stop mastools upgrade

Stopped all mastools processes.

Python 3.9.16

Copying custom certs from /var/mastools/cert/custom_cacerts/

Cannot open /var/mastools/cert/custom_cacerts/*.pem

Starting mastools in registered mode.

Mastools processes started.

could the mastools os version mismatch be the problem, how can i update the mastools version?

The output looks exactly like it should. NetScaler's didn't show up on Console Service, even after some minutes (5-10) after your setup? All required URL's and Ports are also allowed from NSIP to outgoing Internet?

yes all urls are allowed and dns works

do you need a proxy for inet access ? i am sure there is proxy .py script that i had to setup before

No don‘t use a prox

I replied on the blog post as well. If you re-run the command, do the tools now show the same version? Honestly, I have not tried it since LAS was released. Let me go and give it a try on a new VPX and see if I see the same behavior.

Hi Richard, thanks for the anwer. Yes I tried to rerun it but the result is always the same

built-in agent supports LAS now? I must have missed that one

It is not looking that way. Trying to verify now.

Yes we already have successfully regisered another netscaler with the Buildin agent

Technically its working (doing that for some of my lab instances, too) but I also wondered if its official supported or you have to use the Agent.

Intereseting, I wonder what version enabled that.

When I was at a PTEC meeting (a while ago admittedly) I complained to the PMs about having to have an agent deployed requiring an expense if you are in the cloud and a minimum of 4 CPU and 8 GB RAM just to license the appliance. Their answer was "Why don't you use the built-in agent?" which resulted in my trip down the rabbit hole to locally set the built-in agent and write a blog about it. I am going to say the PMs expect that it is supported. 😎

I was quite unhappy having to deploy ADM in multiple of my clients cloud environments and not being able to charge them for it, yes, it's BS.

Good man.

on the netscaler instances where the buildin agent worked, we got this output:

running image upgrade

Download site signature verification successful

VPX registration with device profile provided

----------------------------------------------------------------------------

NetScaler Console Tools successfully registered.

----------------------------------------------------------------------------

14.1-69.31

re-registration, invoke the binary

Stopping mastools processes...

Using new method to stop mastools upgrade

Stopped all mastools processes.

Python 3.9.16

Copying custom certs from /var/mastools/cert/custom_cacerts/

Cannot open /var/mastools/cert/custom_cacerts/*.pem

Starting mastools in registered mode.

Mastools processes started.

built-in agent supports LAS but for me I am having other weird issue with the latest VPX build and getting onboarded before I can even get to the LAS part