Does NSC -> VPX LAS licensing traffic still use 27000 / 7297? Or is it all now 443 / 22? FWIW, I found this @ docs.netscaler.com for NSC Service, I'm assuming it's similar for on-prem NSC? Context: our monitoring platform showed our NSC on 14.1 60.57 started alerting that port 27000 closed around 5pm yesterday (which lines up with the 15th of April + 14 days GMT-7 ironically), but I still see PushLASLicense tasks being completed in NSC logs, and looking VPXs individually and the licensing tab in NSC, they all appear to still be licensed.

Yeah, the fact that the ports are closed are spot on, yesterday I could telnet to the ports on a new instance, today, I couldn't, and I assumed it was the firewalls acting up, but then I looked at an old instance that I knew could also telnet.. no dice. So there's definitely something new happening.. this is also on an on-prem Console.. which is even more amusing.

I just blamed our NSX guy... and now I owe him 🍺

Indeed, previously you had to open 27000 directly to Console. With LAS you finally can leverage all traffic over the agent.

The on premises console is now just a licensing agent as far as I know, and LAS talks to the cloud licensing in 443.

Hehe, was about to say. Yeah, I agree, that's my take on it, too.

Thanks all, sounds like I'm deleting the 27000 and 7297 port monitors today.