Access alternatives

  • CAS ► Reports ► Explore ► Traffic discovery

  • On the CAS, open the Dashboard and click the Discovery tile.

    Discovery tile

Report contents

For everyone, the Discovery reports:

  • Work out of the box, with zero configuration.

  • Provide instant answers to questions such as

    • What’s your total bandwidth usage?

    • Which protocols, VLANs, or tunnels are taking up your bandwidth?

    • Where are your application clients and what performance are they getting?

    • What software services are present in your monitored network and what’s their performance from the data center point of view?

    • If you have Citrix deployed in my network, what is the application delivery performance?

  • Help you identify anomalies in usage patterns.

  • Provide a starting point in deciding which software services and applications you should monitored in depth.

How you in particular use DC RUM's Discovery reports may be determined more by your role:

Alternatively, how you use DC RUM's Discovery reports could be determined more by the situation:

Network engineers

  1. CAS ► Reports ► Explore ► Traffic discovery

    As a network engineer, you probably want to start with a glance at the Discovery Overview report to get a quick idea of the state of your network: overall bandwidth usage, number of VLANS, number of tunnels.

    There are three other distinct overview sections here, but you might want to start with the Discovery - Network report.

  2. Discovery - Network

    Drill down to the Discovery - Network report to get a better idea of what's going on with bandwidth, VLANS, and tunnels. This report also breaks down bandwidth usage by protocol and QoS. You're probably interested in which protocols take the most bandwidth and how their consumption of bandwidth changes over time. That helps you detect any deviations from the daily usage pattern.

  3. Sites and links

    From here, check the Sites and links tab to see which sites are using data center resources and how much of the available bandwidth they are utilizing.

    DC RUM automatically detects and identifies sites based on predefined private network ranges, autonomous system numbers, or a CIDR blocks. For all detected sites, it provides information on bandwidth usage and IP node activity. This is concisely presented in the Sites and links report. Currently active sites and links (when defined or detected from Netflow records) roughly tell you whether your datacenter is used by users from an expected number of locations.

    The number of active IP nodes tells you about the IP address activity in the network and helps spot deviations from the daily pattern.

    Again, like with protocols, VLANs or tunnels, seeing the locations occupying the biggest chunk of the bandwidth helps you determine whether everything is as usual and, if there are anomalies in usage, you can easily spot them without any configuration.

    If you’re interested in drilling down for more detail, DC RUM provides the full network-oriented workflow, starting from Sites.

Service and application owners

  1. CAS ► Reports ► Explore ► Traffic discovery

    As an application owner, it may be more important for you to see how your services and applications are performing (though the network aspect as described above will also matter to you).

    You probably want to start with a glance at the Discovery Overview report to get a quick idea of the state of your network: overall bandwidth usage, number of VLANS, number of tunnels.

    There are three other distinct overview sections here, but you might want to start with the Discovery - Network report.

  2. Discovery - Services

    Drill down to the Discovery - Services report to see the bandwidth usage for the top three tiers present in the monitored environment.

    As with the Network section, for application owners it’s crucial what software services take most of the bandwidth and whether there are any deviations from daily patterns. That applies to services hosted in the datacenter as well as to those hosted in the cloud.

    In addition, DC RUM tells you whether end users suffer from DNS or LDAP issues or Windows domain access service issues, which are problems related to netlogon operations or slow network drive mapping operations.

    This intelligent problem detection doesn’t require any configuration; everything is detected out of the box.

Citrix administrators

  1. CAS ► Reports ► Explore ► Traffic discovery

    As an Citrix administrator owner, the entry point for this audience is the Citrix section, where DC RUM displays bandwidth usage as a confirmation that the platform is working and that there are no deviations from the daily pattern.

  2. Discovery - Citrix

    DC RUM can discover and automatically provide information on bandwidth usage for applications delivered by Citrix based on traffic analysis as well as on the Citrix AppFlow data feed.

    As a Citrix owner, you can immediately learn whether your applications are used as per daily patterns, and if there are any anomalies spotted, you can continue with fault domain isolation or navigate to the Citrix status dashboards.

Out of the box

After you direct DC RUM to your devices, DC RUM's Discovery reports automatically start delivering answers to you right out of the box.

  1. Check Discovery reports to see the results.

  2. Review the information at the Overview level before deciding whether you need to go further.

    • Bandwidth is your primary metric for network performance monitoring. On the Bandwidth usage chart, is the shape of the current bandwidth usage the same as the baseline (last week's bandwidth usage)? If not, drill down to see where the anomalous bandwidth usage is coming from.

      Do you have the expected numbers for the VLANs and Tunnels totals? If not, you could have a security problem.

      For more information, see Discovery - Network report.

    • Does Active nodes show the expected number of IP addresses? If not, maybe part of your network is down or is not being monitored properly.

      For more information, see Discovery - Sites and links report.

    • Do the Website, Database, or Middleware charts look normal to you? Are they shaped like the baselines? If not, there may have anomalous activity on one of these tiers.

      For more information, see Discovery - Services report.

    • Is Citrix traffic as expected?

      For more information, see Discovery - Citrix report.

  3. Check the Diagnostics tab for device performance and capture traffic on devices reporting anomalous performance.

    For more information, see Traffic diagnostics report, Secure traffic diagnostics report, and Capturing packets on AMD.

Responding to an alert

Regular users of DC RUM find the Discovery reports helpful in monitoring everyday performance.

  1. Check Discovery reports to see whether anything out of the ordinary is being reported. The main Discovery report shows you all the quick indicators you might normally need:

    • Current and baseline bandwidth usage in general, per tier, and on Citrix if applicable.

    • Current and baseline bandwidth usage per tier (website, data center, database)

    • Current and baseline bandwidth usage on Citrix (if applicable).

    • Number of VLANs

    • Number of tunnels

    • Number of active nodes

    • Number of sites

    • Number of links

    Use these graphs and counts as a dashboard you can check at a glance.

  2. If something looks unusual, go to the Diagnostics reports to track down the cause and determine the solution.

    For more information, see Traffic diagnostics report.

  3. After you fix the problem, return to Discovery to verify that you have cleared up the problem.

Alternatively:

  1. You see a yellow triangle or a red "!" at the report heading.

  2. Hover over the tooltip to read the alert.

  3. If the issue is related to the AMD, or you anticipate that it could be, go to Diagnostics reports.

  4. When you think you fixed the issue, inspect Discovery reports.

Configuration assistant

  1. Review the current state of your system.

  2. Make your configuration changes.

  3. Return to Discovery to make sure everything is running as planned and you are not experiencing any unwanted side effects.

  4. If anything is wrong, click the Diagnostics tab to start tracking down the problem.

    When you are changing your configuration, Discovery reports, in conjunction with the Diagnostics reports, can help you make sure you get the results you expected.

    Diagnostics should always be used whenever there are changes to SPAN configuration or you add new sniffing points, or when you add SSL keys and create UD services for monitoring secure applications. Diagnostics is a kind of daily check to verify everything is working as expected and there are no deviations from daily patterns. Diagnostics should also be used when you add sniffing points to see more traffic, in which case it's good to watch the result and quickly determine whether your changes are aligned with your intended goal.

    For more information, see Traffic diagnostics report.

 

  • No labels