NetScaler Console service

How to monitor globally distributed sites

As a network administrator, you might have to monitor and manage network instances deployed across geographical locations. However, it is not easy to gauge the requirements of the network when managing network instances in geographically distributed data centers.

Geomaps in NetScaler Console provides you with a graphical representation of your sites and breaks down your network monitoring experience by geography. With geomaps, you can visualize your network instance distribution by location and monitor network issues.

The following sections explain how you can monitor data centers in NetScaler Console.

Monitoring globally distributed sites in NetScaler Console

NetScaler Console site is a logical grouping of Citrix Application Delivery Controller (NetScaler) instances in a specific geographical location. For example, while one site is assigned to Amazon Web Services (AWS) and another site might be assigned to Azure™. Still another site is hosted on the premises of the tenant. NetScaler Console manages and monitors all NetScaler instances connected to all sites. You can use NetScaler Console to monitor and collect syslog, AppFlow, SNMP, and any such data originating from the managed instances.

Geomaps in NetScaler Console provides you with a graphical representation of your sites. Geomaps also breaks down your network monitoring experience by geography. With geomaps, you can visualize your network instance distribution by location and monitor all network issues. You can click Infrastructure on the menu and this displays the Instances Dashboard for a visual representation of the sites created on the world map.

Use case

A leading mobile carrier company, ExampleCompany, was relying on private service providers for hosting their resources and applications. The company already had two sites - one at Minneapolis in the United States and another in Alice Springs in Australia. In this image, you can see that two markers represent the two existing sites.

Site markers

The markers also display the count of the following components on the site:

  • Instances: Indicates the number of instances available.

  • Applications: Indicates the number of applications hosted.

  • Virtual Servers: Indicates the number of virtual servers available.

  • Critical Events: Indicates the count of critical events occurred on the instances.

  • Major Events: Indicates that the count of major events occurred on the instances.

Site components

Click Applications to see all custom applications created in each site.

Click Details to see a list of NetScaler instances added in each site. Click the tabs to view more information:

  • Instances tab: View the following in this tab:
    • IP address of each network instance
    • Type of the NetScaler instance
    • Number of critical events
    • Significant events and all events raised on a NetScaler instance.
  • Events tab: View a list of critical and significant events raised on the instances.
  • Certificates tab: View the following in this tab:
    • List of certificates of all the instances
    • Expiration status
    • Vital information and the top 10 instances by many certificates in use.
  • Agents tab: View a list of agents to which the instances are bound.

Application details

Configuring Geomaps

ExampleCompany decided to create a third site in Bangalore, India. The company wanted to test the cloud by offloading some of their less-critical, internal IT applications to the Bangalore office. The company decided to use the AWS cloud computing services.

As an administrator, you must first create a site, and next add the NetScaler instances in NetScaler Console. You must also add the instance to the site, add an agent, and bind the agent to the site. NetScaler Console then recognizes the site that the NetScaler instance and the agent belong.

For more information on adding NetScaler instances, see Adding Instances.

Create a Site

Create sites before you add instances in NetScaler Console. Providing location information allows you to precisely locate the site.

To create a site:

  1. Navigate to Infrastructure > Instances > Site. Click Add.
  2. On the Select Cloud tab, choose the Site type. You can create a site of type Data Center or Branch.

    Select site

    For Data Center site type, select the Type from the list:

    • Private
    • AWS
    • Azure
    • Google Cloud
    • VMware vCenter

    Select data center

    Click Next.

  3. On the Choose Region tab, enter the following details:

    • Site Name
    • City
    • Zip Code
    • Region
    • Country
    • Latitude
    • Longitude

    Choose a region

    Alternatively, you can enter the location in Search Location and click Get Location to precisely locate the site. The City, Zip code, Region, Country, Latitude, and Longitude fields are automatically filled in.

    Get location

    Click Next.

  4. On the Configure ITM Radar tab,

    1. Select Radar URL in the Real User Measurements list.
    2. Enter the URL.

    Get location

    Ensure that the URL has the following format:

    http(s)://[ip-or-fqdn]/[path-to-r20.gif], and the path ends with /img/r20.gif.

    An error message appears if the entered URL is incorrect or if you are unable to access the URL. Ensure that the URL is valid, correctly formatted, and functional.

    Click Finish.

Notes:

  • For site type, Data Center (Private or VMware vCenter), and Branch, you must provide a Radar URL during configuration.
  • For AWS, Azure, and Google Cloud, instead of entering a URL, you can select the appropriate Radar Region from the Real User Measurements list.
  • If you enable the Fetch option specific to each cloud provider:
    • For AWS: Fetch VPC from AWS
    • For Azure: Fetch VNet from Azure
    • For Google Cloud: Fetch Regions from Google Cloud

    You don’t have to select a Radar Region separately. In this case, you have to select either Enabled or Disabled from the Real User Measurements list.

Configure ITM Radar for cloud provider types

You can create a site with a cloud provider type and choose whether to enable or disable the Fetch option. By default, the Fetch option is not selected.

Scenario 1: Cloud provider configuration without Fetch option

  1. Select cloud provider type:

    • On the Select Cloud tab, select the Data Center site type.
    • Select the cloud provider type as either AWS, Azure, or Google Cloud and click Next.

      Select Cloud

  2. On the Choose Region tab, enter the necessary details and click Next.

    Choose aws region

  3. On the Configure ITM Radar tab, select Radar Region from the Real User Measurements list.

  4. Select the Public Cloud Region from the set of predefined lists available for the specific cloud provider.

    Radar Region

  5. Click Finish.

Scenario 2: Cloud provider configuration with Fetch option

  1. Select cloud provider type:

    • On the Select Cloud tab, select the Data Center site type.
    • Select the cloud provider type as either AWS, Azure, or Google Cloud and enable the Fetch option.

      Enable Fetch

    Click Next.

  2. On the Choose Region tab, select the following:

    • Cloud Access Profile
    • Region
    • Network(VPC)

      Enable Fetch

    Based on your selection, the Site Name, Latitude, and, Longitude are automatically filled in.

    Click Next.

  3. On the Configure ITM Radar tab, select enabled or disabled from the Real User Measurements list.

    ITM Radar Fetch

    Click Finish.

Edit a Site

To modify an existing site:

  1. Select the site and click Edit.

  2. On the Configure Site page, you can update the Site type. For example, if you have selected Branch previously, you can update to Data Center.

  3. Depending on the site type, you can modify the Type. For example, you can change the type from a Private Data Center to a Public Cloud from the list.

  4. Update the Real User Measurements based on your previous selection. If you have initially provided a Radar URL, the system dynamically adjusts the fields to a Radar Region or vice versa based on your preference.

Automate radar object deployment

You can automate the deployment of the radar object (r20.gif) by directly installing the r20.gif file into the respective NetScaler instances. This feature is available only for Data Center (with type Private) and Branch site types and can be accessed only when editing a site, not during site creation.

To modify an existing NetScaler Console site with ITM Radar option enabled and deploy radar objects to a NetScaler instance, follow these steps:

  1. Navigate to Infrastructure > Instances > Sites.
  2. Select the site and click Edit. Ensure that the site is ITM Radar enabled.
  3. On the Configure Site page, select Deploy to NetScaler from the Real User Measurements list.
  4. From the NetScaler Instance list, select an instance where you want to deploy the radar object.
  5. Click OK.

Select NetScaler instance

When you click OK, the Intelligent Traffic Management runs a Radar Object Policy StyleBook on the chosen NetScaler instance.

The Radar Object Policy StyleBook helps in installing the radar object on the specific NetScaler, allowing the NetScaler to handle requests for the r20.gif radar URL.

In the Radar Object Policy StyleBook, specify the Config Key for the Config Pack and select the NetScaler instances.

Radar StyleBook

Delete a Site

  1. To delete a site, select the site and click Delete.
  2. On the Confirm page, click Yes.

To add instances and select sites:

After creating sites, you must add instances in NetScaler Console. You can select the previously created site, or you can also create a site and associate the instance.

  1. In NetScaler Console, navigate to Infrastructure > Instances > NetScaler.

  2. Select the VPX, and click Add.

  3. On the Add NetScaler VPX page, type the IP address and select the profile from the list.

  4. Select the site from the list. You can click the Add button next to Site field to create a site or click the Edit button to change the details of the default site.

  5. Click the right arrow and select the agent from the list that displays.

    Select agent

  6. After choosing the agent, you must associate the agent with the site. This step allows the agent to be bound to the site. Select the agent and click Attach Site.

    Associate agent to site

    1. Select the site from the list and click Save.
  7. Optionally, you can enter key and value fields for Tags.

  8. Click OK.

You can also attach an agent to a site by navigating to Infrastructure > Instances > Agents.

To associate an agent with the site:

  1. In NetScaler Console, navigate to Infrastructure > Instances > Agents.

  2. Select the agent, and click Attach Site.

  3. You can associate the site and click Save.

NetScaler Console starts monitoring the NetScaler instances added in the Bangalore site along with the instances at the other two sites as well.

To export the report of this dashboard:

To export the report of this page, click the Export icon in the top right side of this page. On the Export page, you can do one of the following:

  1. Select Export Now tab. To view and save the report in PDF, JPEG, PNG, or CSV format.

  2. Select Schedule Export tab. To schedule the report daily, weekly, or monthly and send the report over an email or a slack message.

Note:

  • If you select Weekly recurrence, ensure that you select the weekdays on which you want the report to be scheduled.
  • If you select Monthly recurrence, ensure that you enter all the days that you want the report to be scheduled separated by commas.
How to monitor globally distributed sites