Monitor SystemEDGE-enabled Devices with the snmpcollector Probe

CA SystemEDGE is a lightweight agent that provides monitoring of physical and virtual systems. System administrators use CA UIM, the CA SystemEDGE agent, and the snmpcollector probe, to monitor Key Performance Indicators (KPIs) of their SystemEDGE-enabled systems. 
This article is for the
snmpcollector probe v3.3 and later
Conceptual Overview
SystemEDGE is a lightweight agent that provides local monitoring of physical and virtual systems and remote monitoring of virtual environments. System Administrators can incorporate monitoring of their SytemEDGE-enabled systems into their 
CA Unified Infrastructure Management
 installations through the snmpcollector probe. You import SystemEDGE-enabled devices to be monitored using the CA UIM Discovery process. You then apply monitoring to one or more SystemEDGE-enabled devices using the snmpcollector probe. Using the snmpcollector probe, you can monitor Key Performance Indicators (KPIs) for these devices. KPIs include: configuration, performance, files, and more. Optionally, you can monitor these KPIs based on specified thresholds or conditions. You view the monitoring data in the 
CA Unified Infrastructure Management
 visualization components, including USM or the Default CA Business Intelligence Summary Dashboards.
The following diagram shows the workflow for monitoring SystemEDGE-enabled devices with the snmpcollector probe:
Verify Prerequisites
  • The following 
     software versions on the primary hub:
    • CA Unified Infrastructure Management server version 8.5 or later
    • discovery_agent and discovery_server (the same version as CA Unified Infrastructure Management server)
    • the latest version of the ci_defn_pack where the nis_server is installed  
    The following 
     probe packages in the local archive on a hub: 
    • snmpcollector v3.30 or later
    • the latest version of ppm (automatically installs prediction_engine and baseline_engine)
  • (Optional) Install CA Business Intelligence with 
    CA Unified Infrastructure Management
     8.5 or later.
    : If you want to run the optional SysEdge On Demand Report, then install the cabi probe version 2.0 with CA UIM, version 8.5.1 or later, and the snmpcollector probe 3.31 or later. For more information about the specific prerequisites for the OnDemand Report, see the procedure on this page titled "Run the SysEdge On Demand Report".
Find SystemEDGE-enabled Devices Using Discovery
Discovery Wizard enables you to efficiently identify many SystemEDGE-enabled devices to monitor in your environment. Use Discovery Wizard if you do not know how many or what SystemEDGE-enabled devices are in your environment.
If you do already know which SystemEDGE-enabled devices you want to monitor, you can add individual device profiles or import devices to snmpcollector with a file. For more information about how to add individual device profiles or to import devices to snmpcollector with a file, see snmpcollector Import Devices.
The first time that you open the Unified Management Portal (UMP), the Unified Service Manager portlet opens and the Discovery Wizard launches. You can also launch the Discovery Wizard whenever you want to run discovery or change your discovery settings. You can launch the Discovery Wizard from the Inventory node or from the Actions menu.
: The Discovery Wizard will not run after an update of CA Infrastructure Management if there are existing range scopes that define excluded IP addresses. Either accept the system prompt to delete excluded range scopes or remove them manually from the database. Then, discovery runs.
Follow these steps:
  1. Hover the cursor over the name of a discovery_agent or range in the tree or click on it. The magnifying glass icon indicates discovery_agents. The network icon indicates ranges.
  2. Click the gear icon to the right of the discovery_agent or range name in the tree, or select 
    Discovery Wizard
     from the Actions menu.
Create SystemEDGE Authentication Profiles
Authentication profiles allow you to create, edit, view, and delete authentication profiles for discovery. A profile contains credential information necessary to access and gather information about the computer systems and devices in your network.
You can create one or more SystemEDGE authentication profiles using the SNMP tab. Create as many SystemEDGE authentication profiles as you need.
To enable monitoring by the SystemEDGE agent, you must select SNMP v1 when you create a SystemEDGE authentication profile.
Follow these steps:
  1. Click 
    New credentials
     in the left pane.
  2. Enter information in all required fields. Required fields are outlined in red.
    : You can reuse authentication profile names once the previous profile is deleted.
  3. Click 
    . The information that you enter is saved when you click Next and move through the Discovery Wizard.
    1. To view the properties of an existing profile, select the appropriate authentication tab and then select a profile in the left pane.
    2. To modify an existing authentication profile, select the profile and edit the fields as necessary, and then click 
      . To delete an authentication profile, click the trash can icon next to the name of the profile in the left pane, and click 
(Optional) Create Range Scopes
You can the limit the discovery of SystemEDGE-enabled devices to range scopes that you define.
Follow these steps:
  1. Click 
    New range scope
     in the left pane of the Scopes tab.
  2. Enter a name for the range scope.
  3. In the Range Scope definition section, specify the area of your network where you want to perform discovery.
     - A mask defines a subnet using Classless Inter-Domain Routing (CIDR) notation with a base IPv4 address and a routing prefix. For example, The value /24 refers to a Class C subnet of 256 addresses. Other values for reference: /30 (4 addresses) and /16 (65,536 addresses, or a Class B subnet).
    Note: When you enter a subnet mask, the number of IP addresses the mask represents is displayed (the number of effective hosts minus two). Only /16 subnets or smaller are supported.
     - Range of IPv4 addresses.
    Single IPv4 or IPv6 address
    . You can use abbreviated IPv6 address forms, and IPv6 addresses that refer to IPv4 addresses. However, anycast, multicast, link-local, and loopback addresses are not supported.
  1. Click New IP range or single IP address to add another IP range, address, or mask if desired.
  2. In the Credentials section, you can assign authentication profiles to the selected range. By default, all the authentication profiles are selected. If you have many authentication profiles in the list, you can enter the name of a profile to filter the list.
  3. To view only the profiles that are selected, click the Hide unused credentials check box.
Run Discovery
In the Schedule tab, you can schedule discovery to run in the future or you can run discovery immediately. You can schedule either a single discovery run or recurring runs.
A scheduled discovery does not interrupt a discovery that is already running. If at the time a discovery run is scheduled another discovery run is in progress, the scheduled discovery is ignored.
If you select 
Run discovery now 
and discovery is in progress, the current discovery run is terminated and the new run is executed.
Follow these steps to start and/or schedule discovery:
  1. To run discovery, leave the 
    Run discovery now
     checkbox selected.
  2. To schedule discovery, select the 
    Schedule discovery
     check box.
  3. Enter information in the date and time fields.
    The time field is in 24-hour format. The time is the local time of the user.
  4. To schedule recurring discovery runs, select the 
    Recurring every 
    check box, and enter the number of hours for the recurrence interval.
  5. Click 
    to complete the Discovery Wizard.
For more information about Discovery, see Run Discovery in USM on the 
CA Unified Infrastructure Management
SystemEDGE Monitoring Best Practices
Consider setting up and configuring three separate instances of the snmpcollector probe to improve the efficiency of monitoring both SNMP and SystemEDGE-enabled devices, both physical and virtual:
  1. Instance one of the snmpcollector probe monitors SNMP-enabled devices.
  2. Instance two of the snmpcollector probe monitors SystemEDGE-enabled devices in general.
  3. Instance three of the snmpcollector probe monitors SystemEDGE-enabled devices hosting AIMS, such as VMs and LPARs.
    Virtual devices are more dynamic than physical devices, therefore you might discover virtual SystemEDGE-enabled devices, especially those hosting AIMS, more often than you discover other types of devices. Using a separate instance of the snmpcollector probe to monitor these devices enables you to more frequently discover new devices, or to drop unavailable devices, only on that instance. The performance of the other two instances of the probe are unaffected by this frequent discovery.
Configure snmpcollector
To import data about the SystemEDGE-enabled devices in your system, the snmpcollector probe uses a secondary discovery process, in addition to the initial discovery process in USM. You also configure the snmpcollector probe to monitor the SystemEDGE-enabled devices that you discovered in your system using the initial discovery process in USM.
To configure the snmpcollector probe to monitor SystemEDGE-enabled devices:
  1. Set the path to the Discovery Server.
  2. (Optional) Enable auto-templates to automatically apply the SystemEDGE template configuration to a device when it is discovered by the secondary discovery process for the snmpcollector probe.
  3. (Optional) Add discovery filters for the snmpcollector probe to restrict the number of devices you receive from discovery_server. 
If you already know which SystemEDGE-enabled devices you want to monitor, you can add individual device profiles or import devices to snmpcollector with a file. For more information about how to add individual device profiles or to import devices to snmpcollector with a file, see snmpcollector Import Devices.
Set the Path to Discovery Server
Set the path to the discovery_server probe, which must be installed and running on your 
CA Unified Infrastructure Management
 primary hub. The probe generates device profiles that are based on the information from discovery_server.
Follow these steps:
  1. In the probe configuration GUI, click the Discovery Filters node in the tree.
  2. Enter the path to the discovery_server probe in the 
    Discovery Server Address
    The path must be the complete path, in the following pattern:
  3. Click 
(Optional) Enable Auto-Templates
To apply the SystemEDGE template configuration to a device as soon as it is added to the snmpcollector probe, enable auto-templates.
Follow these steps:
  1. In the probe configuration GUI, select snmpcollector node.
  2. In the 
    Probe Configuration
     section, select 
    Enable Auto-Templates
  3. Click 
(Optional) Add Discovery Filters
You have the option to configure filters to restrict the number of devices that you receive from discovery_server. You can use one or more of these filters to control the list of available monitoring targets. The monitoring targets are the devices that appear under the Profiles node in the probe configuration GUI. You apply the filters when you manually import devices from discovery_server.
 Add filters before you manually update discovery. The probe only applies filters to new devices.
Follow these steps:
  1. In the probe configuration GUI, click the 
    Discovery Filters 
    The path to the discovery_server probe must be set to use these filters. 
  2. Enter information in one or more filters to restrict the number of devices. 
  3. Click 
     to add a filter to a table.
    The following filters are available:
    • Discovery Scopes - Restrict devices by IP address (, IP range (, or subnet mask (
    • discovery_agents - Restrict devices by the agent address, robot with the agent, or IP address of the robot with the agent. The agent address must be the complete path, following the pattern /<domain>/<hub>/<robot>/discovery_agent.
    • Discovery Origins - Restrict devices by origin. The origin is a name that is assigned to QoS data from probes to identify the origin of the data. If you are an MSP, for example, typically the origin is the name of each customer. For enterprise customers, typically the hub name is used.
      When you add information to a discovery scope, discovery_agent, or discovery origins filter, the data entry field appears below the filter table.
       to add more rows to the table or 
       to remove a selected filter in a table.
    • (v3.3 and later) Device Services - Restrict devices by the service, such as SystemEDGE.
  4.  Select the desired 
    Device Service Filter
     from the Available menu.
  5.  Click 
    . The filters are active the next time you manually import profiles from discovery.  
For more information about how to apply monitors using the snmpcollector probe, see snmpcollector (SNMP Data Monitoring).
View Data in USM
The Unified Service Manager (USM) portlet lets you visualize and organize your infrastructure, and configure monitoring in CA UIM.
The dynamic and flexible grouping features allow you to organize your infrastructure into an unlimited hierarchy of groups and subgroups. You can organize groups according to concepts, such as service, customer, organization, or technology. Membership in groups is managed automatically based on rules that you define that filter on device attributes. You can add an advanced filter to limit a group based on an advanced attribute, such as SystemEDGE.
For more information about how to create and manage groups in USM, see the Unified Service Manager Portlet.
View Data in the CA Business Intelligence Summary Dashboards
Before you can view data in the CA Business Intelligence Summary Dashboards, you must first install CA Business Intelligence with CA UIM. For more information, see Install or Upgrade CA Business Intelligence with CA UIM.
(Optional) Run the SysEdge On Demand Report
The SysEdge On Demand Report provides on demand reporting for devices that are enabled with the CA SystemEDGE agent and monitored with the snmpcollector probe. The SysEdge On Demand Report includes descriptive details that are captured by SystemEDGE agents about: assets, components, processes, and installed software.
Verify the OnDemand Report Prerequisites
To run the report, first meet the prerequisites.
Install the Required Probes and Packages
  1. Verify that you installed snmpcollector 3.31 and 
    CA Unified Infrastructure Management
  2. Install the cabi probe. The cabi probe installs CABI Server and enables the CA Business Intelligence with CA UIM. For information about how to install or upgrade CA Business Intelligence Dashboards, see Install or Upgrade CA Business Intelligence with CA UIM.
  3. On the CABI Server robot, install the  CA UIM RESTful webservices "webservices_rest" package.
  4. On the CABI Server robot, install the OnDemand data source "cabi-sysedge-datasource" package.
  5. Restart the wasp probe.
Create the Data Source
The SysEdge On Demand Report requires that you create a bean data source for it.
Follow these steps
  1. Access the CABI Server.
    In USM, click Unified Dashboards, CA Business Intelligence. Click the CABI Server Home link. No password is required.
  2. For Data Sources, click 
  3. From the drop-down menu, select 
    Bean Data Source
  4. Enter the Bean Name:
  5. Enter the Bean Method:
  6. Test the connection.
  7. Save the bean data source in the data source folder /public/ca/uim/Datasources as:
    sysedge datasource
    : If you give the bean data source a name other than 
    sysedge datasource
    , the data source will fail.
  8. On the robot where you installed the CABI Server and SystemEDGE, edit the database properties file.
    1. Go to your 
      CA Unified Infrastructure Management
       installation directory> /nimsoft/probes/service/wasp/webapps/cabijs/WEB-INF.
      For example, on Windows systems this is typically:
      program files x86/nimsoft/probes/service/wasp/webapps/cabijs/WEB-INF
    2. Open the file:
    3. In the file:
      • Enter your database type and connection details.
      • Enter your CA UIM username and password.
        : When you enter your credentials in the file on your local system, they appear in plain text. However, when you run the report for the first time, your credentials are rewritten to the file in an encrypted form.
      • Modify the code block for your database type. For example, Oracle:
        #Oracle Connection properties
        #Active connection eg. mysql/mssql/oracle
        #UIM component credentials
    4. Save the file.
    You created the data source for the report.
Install the OnDemand Report Package
On the CABI Server robot, install the OnDemand report "cabi-sysedge-report" package.
Run the Report
You run the report from the CA Business Insight Summary Dashboard page. The Reports drop-down list appears on the Summary Dashboard page 
 after you select the relevant device.
Follow these steps
  1. In the Summary Dashboard, select the systemEDGE device for which you want to run the report.
    The Device Summary Dashboard opens.
  2. In the Device Summary Dashboard, click the Reports drop-down list and select the SysEdge On Demand Report.
    Device Summary Dashboard.png
    A Report Viewer window pops up. Because the report fetches data on demand from the SystemEDGE-enabled devices monitored by the snmpcollector probe, it takes some time for the report to load.
 SysEdge Report.png 
Use the Report
  • To navigate to a specific category in the report, click on the category title in the Table of Contents.
  • To expand or collapse a category in the report, click on the icon to the left of the category title.
  • To filter or sort, click on the header at the top of any column in the report.
    Tool Tip
    : You can filter or sort on multiple columns to focus only on the data that interests you.