net_connect AC Configuration

This article is for probe versions 3.2 and later.
uimpga-ga
net_connect_AC
This article describes the configuration concepts and procedures to set up the Network Connectivity Monitoring (net_connect) probe. You can configure the probe to monitor the availability of remote systems. The probe allows you to create host profiles that use ping commands (ICMP ECHO) to verify the connection between the host and the targeted remote system. You can also configure the profiles to monitor TCP-based services such as telnet and http on the host.
 
This article is for probe versions 3.2 and later.
 
The following diagram outlines the process to configure the probe.
net_connect_AC_Config
net_connect_AC_Config
 
Contents
 
 
 
2
 
 
Verify Prerequisites
Verify that required hardware and software is available before you configure the probe. For more information, see net_connect (Network Connectivity Monitoring) Release Notes.
Configure General Properties
You can set up the following general properties of the probe:
  • Logging details
  • Monitoring interval
  • Network interface
  • Performance properties
You can also create the TCP services that the probe can monitor.
 
Follow these steps:
 
  1. Open the 
    net_connect
     node.
    The 
    Probe Information 
    section provides information about the probe name, probe version, start time of the probe, and the probe vendor. 
  2. Set or modify the following fields in the 
    General Configuration
     section to configure the logging, interval, and network interface details:
    •  
      Log File: 
      displays the file where the probe logs information about its internal activity.
      Default: net_connect.log
    •  
      Log Size(KBytes)
      : specifies the size of the log file where the internal log messages of the probe are written, in kilobytes. When this size is reached, new log file entries are added and the older entries are deleted.
      Default: 100
    •  
      Log Level: 
      specifies the level of details that are written to the log file. You can select the following log levels:
      • 0 - Logs only severe information (default)
      • 1 - Logs error information 
      • 2 - Logs warning information 
      • 3 - Logs general information 
      • 4 - Logs debugging information 
      • 5 - Logs tracing/low-level debugging information
         Log as little as possible during normal operation to minimize disk consumption, and increase the amount of detail when debugging.
    •  
      QoS Interval: 
      specifies the time interval that the probe waits before it generates QoS messages.
      Default: 5
      Reduce this interval to increase the frequency of QoS messages. A shorter interval can also increase the system load.
    •  
      QoS Interval Unit: 
      specifies the unit for the 
      QoS Interval
       field.
      Default: min 
    •  
      Bind to network interface: 
      allows you to bind all network operations to the controller IP address.
      Default: Not selected 
    •  
      Force service check: 
      enables monitoring of services even if the ICMP connectivity fails.
      Default: Not selected
  3. Set or modify the following fields to configure the performance properties of the probe:
    •  
      Max Ping Threads: 
      specifies the maximum number of host profiles that you can execute simultaneously to monitor ping responses.Default: 100
    •  
      Max Service Threads: 
      specifies the maximum number of host profiles that you can execute simultaneously to monitor services.
      Default: 10
    •  
      Max Packet Loss Threads: 
      specifies the maximum number of host profiles that you can execute simultaneously to monitor the packet loss, jitter, and latency.
      Default: 10
       Increase these values to increase the number of simultaneous host profiles. Larger values can also increase the system load.
  4. Create, modify, or delete the service definitions that the probe can monitor.
  5. Click 
    Save
    .
Create Service Definitions
You can create service definitions that the probe can monitor. The probe monitors the defined ports.
 
Follow these steps:
 
  1. Navigate to the 
    net_connect
     node.
  2. Under 
    Service Definitions
     section, click 
    New
    .
  3. Specify a name for the service in the 
    Service Name
     field.
  4. Specify the port that is monitored for the service.
  5. Click 
    Save
    .
  • To modify an existing service, select a service from the list and specify the details.
  • To delete an existing service, select a service from the list and click 
    Delete.
     
Create Host Profile
You can create host profiles for systems on the network that probe monitors. Host profiles allow you to specify conditions for alarm and QoS messages. 
 
Follow these steps:
 
  1. Click the 
    Options (icon)
     next to the 
    net_connect
     node.
  2. Select 
    Add New Host
    .
    The 
    Add New Host
     dialog appears.
  3. Set or modify the values in the following fields to configure the host properties:
    •  
      Hostname: 
      specifies the name of the monitored network device.
       You must specify the hostname to create the host profile.
    •  
      IP Address: 
      specifies the IP address of the monitored device.
  4.  
    (Optional)
     Select 
    Dynamic IP Monitoring
     to enable the probe to use hostname for a monitoring profile instead of IP address. The value in the 
    IP Address
     field is ignored.
     You can monitor a host that does not have a static IP assigned using the hostname. This feature is useful where the system IP address are generated from DHCP.  Consider the following points when you use dynamic IP monitoring:
    • The IP address option is not available in the 
      Configuration for QoS and Alarm
       section fields in the 
      Profile
       node.
    • If the Alarm and QoS Source identification methods of an existing host profile are configured as the IP Address, the Alarm and QoS Source are overwritten by the hostname.
    • If the monitored host is not responding, the ${IP} variable does not expand in the alarms.
  5. Click 
    Submit
    .
    The host profile is created as a child node under the net_connect node.
  6. Select the
     
    host name
     
     node.
  7. Click 
    Actions
    Ping
     to verify whether the host can respond to a ping request.
  8. Click the 
    Profile
     node.
  9. Set or modify the following fields in the 
    Host Configuration
     section:
    •  
      Check Interval Value: 
      specifies the time interval that the probe waits before it executes the host profile.
      Default: 5
       Reduce this interval to generate alarms frequently. A shorter interval can also increase the system load.
    •  
      Check Interval Unit: 
      specifies the unit for the 
      Check Interval Value
       field.
    •  
      Active: 
      activates the host profile for monitoring.
      Default: Selected
    •  
      Contact Information: 
      specifies the text that can be used as the 
      $contactinfo
       variable in alarm messages. For example, the name of a contact person responsible for the host.
  10. Click 
    Save
    .
Configure QoS and Alarms
You can configure QoS and alarm conditions and messages for a host profile.
 
Follow these steps:
 
  1. Set or modify the following fields in the 
    Configuration for QoS and Alarm
     section:
     CA does not recommend you to change the QoS and alarm identification methods after initial configuration. If you change the identification methods later, multiple graphs are displayed on the Unified Service Management (USM) Metrics view (one for every value). The probe can also generate multiple alarms. Also, CA recommends you to keep the identification methods identical for both alarm and QoS.
    •  
      QoS Identification method:
       allows you to select a target that is included in the QoS message.
    •  
      QoS Source:
       allows you to select a source that is included in the QoS message.
    •  
      Alarm Identification method:
       allows you to select a target that is included in the alarm message. The probe also uses this value as the source in the alarm message.
    •  
      Enable Packet Loss Monitoring:
       allows you to monitor packet loss metrics.
    •  
      Packets to Send
      : specifies the number of packets to send on each interval.
      Default: 0 
    •  
      Delay between Packets (ms)
      : specifies the delay (in milliseconds) between successive packets.
      Default: 0
       You must specify a non-zero value to generate jitter and latency QoS messages.
    •  
      Override global QoS interval:
       overrides the global settings for QoS interval that are specified in the 
      net_connect
       node.
  2. Click the 
    ICMP
     node and set or modify the following fields to configure alarms for the connection to the host:
    •  
      Monitor ICMP connectivity (ping):
       allows you to send ICMP ECHO requests to the destination and monitor the responses.
    •  
      Packet size
      : specifies the size (in bytes) of the ICMP packets sent.
    •  
      Message OK: 
      allows you to select the message that is sent when connection is available.
    •  
      Message Fail: 
      allows you to select the message that is sent when the connection is not established.
    •  
      Timeout (sec.)
      : specifies the maximum waiting time for a response before generating an alarm.
  3. Select the 
    Response Time
     monitor from the list.
  4. Set or modify the following fields to configure the alarm and QoS messages for response time:
    •  
      Publish Data: 
      allows you to generate QoS messages for the selected monitor.
    •  
      Publish Alarms: 
      allows you to enable alarm generation for the selected monitor.
    •  
      Enable threshold monitoring
      : enables you to generate an alarm when the response from the host takes longer time than the specified threshold.
    •  
      Response Time (ms): 
      defines the duration (in milliseconds) that the probe waits for a response from the host before generating an alarm.
    •  
      Message OK: 
      allows you to select the message that is sent when the monitored response time is lower than the specified threshold.
    •  
      Message Fail:
       allows you to select the message that is sent when the monitored response time is greater than the specified threshold.
  5. Click the 
    Packet Loss
     node and select the required monitor from the list.
    If you only enable the 
    Packet Loss Metric
    , the probe uses the 
    Timeout (sec)
     value (as specified in the 
    ICMP Configuration
     node) as the delay interval between the two sent packets. The probe calculates the time taken to send packets as a product of the 
    Packets to Send
     (as specified in the 
    Profile
     node) and 
    Timeout (sec)
     fields. If the calculated delay interval is more than the profile 
    Check Interval
     time (as specified in the 
    Profile
     node), the probe does not generate QoS and alarm messages.
    For example, if 
    Packets to Send
     = 10 and 
    Timeout (sec)
     = 10, then time taken to send all the packets is 10*10=100 seconds. If the profile 
    Check Interval
     is 60 seconds, the probe does not generate QoS and alarms.
     To use the 
    Delay between Packets(ms)
     value (as specified in the 
    Profile
     node) as the delay interval when only 
    Packet Loss Metric 
    is enabled, create a 
    Set_Delay_For_PacketLoss
     key with 
    yes
     value in the Raw Configure interface > 
    setup
     section. If this key is not defined or set as 
    no
    , the probe uses the 
    Timeout (sec)
     value as the delay interval.
  6. Set or modify the following fields to configure QoS for packet loss. The configuration is only applicable when 
    Enable Packet Loss Monitoring 
    is selected in the 
    Profile
     node.
    •  
      Publish Data: 
      allows you to generate QoS messages for the selected monitor.
       
    •  
      Maximum Jitter:
       defines the maximum value of jitter for each interval. Jitter is only calculated if a delay is specified between packets in 
      Delay between Packets (ms) 
      in the 
      Profile
       node.
  7. Click 
    Save
    .
Configure Service Monitoring
You can configure the probe to monitor TCP based services active on the host. You can create service profiles to generate alarm and QoS messages and configure responses to commands.
 
Follow these steps:
 
  1. Click the 
    Services
     node.
  2. Double-click the required services in the 
    Available
     list to move them to the 
    Selected
     list.
  3. Click 
    Actions
    Create Service Profile
     to create service profiles for the selected services as 
    service name
     nodes.
  4.  
    (Optional)
     Click the 
    Options (icon)
     next to the 
    Services
     node and you can select the following options:
    •  
      Add New Service:
       allows you to directly add a service, using the name. You can also add a service using the service name here and define the service and the port in the probe later.
    •  
      Port Scan:
       allows you to ping multiple services and verify the response.
       You can verify whether one or more service is available for monitoring. Click the 
      Options (icon)
       next to the 
      Services
       node and select 
      Port Scan
      . Double-click the required services in the 
      Available
       list to move them to the 
      Selected
       list and click 
      Submit
      . The probe processes the requests and displays the response in the Response dialog.
  5. Click the 
     
    service name
     
     node and set or modify the following fields to configure handshake settings:
    •  
      Activate Service: 
      allows you to enable the service for monitoring.
    •  
      Handshake Settings:
       allows you to enable the probe to identify the local host to the monitored host.
    •  
      Send on connect: 
      identifies the local machine to the host for SSL purposes.
  6. Click 
    Actions >
     
    Test Connect
     to test connection to the service.
  7. Set or modify the following fields to generate QoS and alarms on the response time of the service:
    •  
      Publish Data: 
      allows you to enable QoS generation for the monitor.
    •  
      Publish Alarms: 
      allows you to enable alarm generation for the monitor.
       
    •  
      Reply in (Seconds):
       specifies the duration (in seconds) that the probe waits for a response from the service before generating an alarm.
    •  
      Retries in Interval:
       specifies the maximum number of retries within the time interval that is specified in the 
      Reply in (Seconds)
       field.
    •  
      Delay Between Retries:
       specifies the time delay between two successive retries.
    •  
      Message OK:
       allows you to select the alarm message when the service responds within the threshold time.
    •  
      Message Fail:
       allows you to select the alarm message when the service responds after the threshold time. 
  8. Set or modify the following fields in the 
    Challenge Response Settings 
    section to configure commands that are sent to the service. Only commands that are supported by the service work.
    •  
      Timeout (ms):
       specifies the maximum time the probe waits for a response from the commands before generating an alarm.
    •  
      Send Command When Connected:
       allows you to specify the command after connecting to the service.
    •  
      Send Command Text:
       specifies the command to be sent for execution. For example, you can configure an SFTP service in the probe to transfer a file. You can then provide the SFTP command and the expected successful output in the 
      Response Must Contain the Text
       field.
    •  
      Response Must Contain:
       allows you to specify the expected text in the response.
    •  
      Response Must Contain The Text:
       specifies the expected text to be searched in the response text.
    •  
      Then Send Command text:
       allows you to specify a second command after executing the first command.
    •  
      Response Must Contain:
       allows you to specify the expected text in the response.
    •  
      Response Must Contain The Text:
       specifies the expected text to be searched in the response text.
    •  
      Then Send Command:
       allows you to specify a third command after executing the first and second commands.
    •  
      Response Must Contain:
       allows you to specify the expected text in the response.
       
    •  
      Response Must Contain The Text:
       specifies the expected text to be searched in the response text.
  9. Click 
    Actions
     
    > Test Response
     to verify the responses of the commands from the service.
  10. Click 
    Save
    .
 You can view the operational state of all the configured services for all host profiles in the probe. Navigate to the 
net_connect
 node, 
Status
 section and select the required service from the list. The service properties and status are displayed in the table.
View Alarm Messages
You can view the alarm messages that are configured in the probe.
 
Follow these steps:
 
  1. Click the 
    net_connect
     node.
  2. Navigate to the 
    Message Manager
     section.
  3. Select the required alarm from the list.
    The alarm properties are displayed in the following fields:
    •  
      Identification: 
      displays a name for the alarm message.
    •  
      Token: 
      displays you to select a unique ID for the alarm message.
    •  
      Alarm Text: 
      displays the error message text.
    •  
      Subsystem string/id: 
      displays the subsystem ID of the alarm message.
    •  
      Severity: 
      displays the alarm severity level.
    •  
      i18n token:
       displays the unique token for internationalization support.