net_connect Troubleshooting

This article contains troubleshooting information for the Network Connectivity Monitoring (net_connect) probe.
uimpga-ga
This article contains troubleshooting information for the Network Connectivity Monitoring (net_connect) probe.
Contents
Probe Generates “Failed to execute in scheduled time” Alarm
Symptom:
The net_connect probe is unable to execute all monitoring profiles within the time interval. The probe then generates a
Failed to execute in schedule time
alarm for the remaining profiles.
Solution:
The problem occurs when the monitoring interval is insufficient to execute all monitoring profiles. You can use one of the following options:
  • Reduce the number of monitoring profiles.
  • Change the monitoring parameters to reduce the processing time of each monitoring profile.
    Some examples to reduce the processing time of a monitoring profile are as follows:
    • Reduce the number of retry attempts to monitor the ICMP connectivity of the host. CA recommends a value of 3. However, if the problem continues, decrease the value to 1.
    • Increase the
      Max Ping Threads
       value if sufficient resources are available.
    • Reduce the number of ICMP burst messages. CA recommends a value of 3. However, if the problem continues, decrease the value to 1.
    • Reduce the timeout value of the monitoring profile. CA recommends a value of 2 seconds.
    • Increase the time interval of the monitoring profile. CA recommends a value of 5 minutes.
The CA recommended values are tested with 6500 profiles on Windows and 5048 profiles on Unix platforms. However, the average response time for profiles must be up to 10 ms. For failure scenarios, response time must be up to 10 percent. If the profile number, average response time, and number of fail scenarios increase, you can modify the recommended monitoring parameters.
Probe Generates a Negative Value for the Packet Latency Metric
Symptom:
The net_connect probe displays a negative value in the
Packet Latency
QoS message.
Solution:
The problem occurs when the packet loss monitoring is enabled and the value of the 
Delay Between Packets
field is low. Then, the probe sends the next packet before receiving the response for the last packet. Increase the value of the
Delay Between Packets
field to resolve this issue.
Probe Generates a Negative Value for the Packet Loss Metric
Symptom:
The net_connect probe displays a negative value in the 
Packet Loss
 QoS message.  
Solution:
Verify the value of the
Delay Between Packets
field and change it to more than zero. For example, 2 milliseconds.