The CUGC Networking Special Interest Group and Healthcare Special Interest Group did a joint webinar covering NetScaler Use Cases in Healthcare + NetScaler and NMAS 12.0 features. Dan Schlimme covered the Healthcare portion of the webinar and Dave Brett (CTP) and myself covered the 12.0 release with Carsten Bruns (CTA) fielding the audience questions in the second half.
Dave and I ran a marathon with 54 slides covering both NetScaler 12.0 and NetScaler MAS 12.0 (Management and Analytics System) firmware releases. We covered new features for both as well as known issues and workarounds we recommend. Lastly we covered what’s coming up in the next 12.0 build and some sessions you can attend at Citrix Synergy 2017 in Orlando where these features will be showcased. We had several hundred live attendees from all over the globe on the webinar and you can watch the recording or download the .mp4 video at the link below. The 12.0 features begin at the 36:55 mark:
https://www.mycugc.org/p/do/sd/sid=242
If you’d like to be a member of either SIG and get notifications on upcoming webinars, you can sign up here:
Networking SIG: https://www.mycugc.org/page/networking-sig
Healthcare SIG: https://www.mycugc.org/page/healthcare-sig
And if you’re headed to Synergy, make sure to register for the CTP hosted sessions. Fellow CTP Bas van Kaam has a list of CTP led sessions here:
See you there!
Chad Tripod
May 23, 2017 at 2:28 AM
There is still more work to be done on the analytics front. It’s nice to see NMAS finally catch up to AVI Networks on the Application Views. I would start to look at counters around TCP and start to make suggestions to admins on their delivery settings (this would just be the beginning). There should be bandwidth saving metrics by implementing HTTP/2.0 over HTTP/1.1. I was sad to see no TLS 1.3 in 12.0 as it has 0 RTT which could be used in conjunction with TFO for better mobile performance. MAS should develop a specific interface for CPX to give visibility into cloud micro-services environments. I like the LogStream because binary protocols like AppFlow are a pain. Still not a fan of the UI. Time to start taking some hard advance looks at Application Delivery. The trends always flow down to enterprise. No need to build for them directly.