Q: Where are the DNS Aliases hosted? I mean entrypoint is a DNS Record? and where is it hosted, ADM Service?

A: Effectively the customer has two options:
1. create an autogenerated alias for multisite applications. This has the format of 01234.abcd.itm.appdeliverysecurity.com. He can then create a DNS CNAME alias in his authoritative DNS provider of his choice, i.e. "app1.customer.com CNAME 01234.abcd.itm.appdeliverysecurity.com"
2. customer can onboard his DNS zone to the NetScaler console service and let NetScaler manage it as a cloud service. in this case he can create app1.customer.com records directly

Q: Availability can be monitored with GSLB also?

A: NetScaler GSLB lacks internet visibility, hence can't detect internet outages that affect the entire datacenter where apps are deployed, an entire Internet Service provider or fine grained combination of ISP + datacenter. NetScaler ITM addresses this gap

Q:  how shall ITM be used with other products at hand?

Q: How do I setup ITM? How do I setup and use Radar? Auth.. DNS? The ITM Dashboard?

A:  To some extent the limited time in today's demo meant that we could only cover the ITM capabilities rather than how to set things up. However, all of these items are extensively covered in our documentation
- You don't need to do anything about dashboard. If you've configured a multisite app, details about it (synthetic monitoring results, requests / second, Geos from where the DNS requests are coming from etc.) are automatically available there. If you've configured Radar for your on-premises datacenter, Radar reports will automatically be available.
- AuthDNS is a cloud managed service documented extensively at https://docs.netscaler.com/en-us/netscaler-console-service/intelligent-traffic-management/itm-authoritative-dns.html
- Setting up Radar is covered under https://docs.netscaler.com/en-us/netscaler-console-service/intelligent-traffic-management/itm-internet-visibility

Q:  Do we have any option to visualise the data flow and find if the failure is outside of Data center i.e the ISP?

A:  Definitely. We didn't look into details of the breakdown facilities that Radar reports offer and how they help triage problems. A typical triaging process consists of the following steps:
- Load the radar performance reports for the datacenter of interest (on-prem, cloud-region, etc.) and look for Availability and RTT deterioration.
- Optionally breakdown per ISP
- In case of a datacenter problem, it will manifest as a measurable availability drop or latency increase across all ISPs.
- If it looks like an ISP problem, one can check the performance of same ISP against other reference platforms we monitor. For example, assume over the last 2 hours our dashboards indicate user experience deterioration of Comcast users accessing our NY on-premises datacenter. We can look at Radar performance reports for Comcast and Azure, GCP and/or AWS us-east regions
- In case of an ISP problem, we expect similar availability or latency deterioration for reference cloud regions.
- Last but not least, there maybe a "blind spot". By principle of exclusion if our DC is good for all ISPs but Comcast and Comcast is good for all cloud regions except but not our DC, then it's the specific Comcast + DC combination at fault. We can reach to our ISP and try to remediate

Q:  How will this be helpful for 1 datacenter with users being statewide only?

A: The monitoring facilities are still useful in identifying and triaging the availability or latency deterioration problem (is it a DC problem? a last-mile one? a combination thereof) and expediting its resolution

Q:  We have ADM on-prem. Are these features only available in the Cloud service (ADM)?

A: Yes, since these are Cloud Services. However, you should be able to combine NetScaler Console Service (for the Intelligent Traffic Management) with on-premises ADM (for NetScaler ADC management)

27 minutes ago, Isha Khurana said:

Q: Where are the DNS Aliases hosted? I mean entrypoint is a DNS Record? and where is it hosted, ADM Service?

It is hosted on ITM servers