Verified Answers

If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it!  Learn more

  • State Verified Answer
  • Replies reply
    1
  • Subscribers subscribers
    18
  • Views views
    151
  • Users 0 members are here
  • +1 person also asked this people also asked this
Related
Options

Ping Latency

ramesh9

Dears

We are planning to have Ping Latency monitoring as per below link,

https://docs.microfocus.com/search/ping%20latency/documentation/Network_Node_Manager_i/24.2

As per the file PingPair.conf, each line should be like this,

Source Details|Destination Details|SourceProxy Details

Now regarding SourceProxy, I want to know we have to have this as L3 or L2 device.

Also what right SourceProxy should contain, so it can start the ping from Source to Destination.

Please clarify.

  • Verified Answer

    +1  

    Hello,

    SourceProxy is optional. If you need to specify one, for example, in MPLS environment, it must be a router (L3 device). Write community name must be enabled on a source router (or, on a proxy one when configured) as well as configured in NNMi for the same device. All devices must be discovered and managed in NNMi.
    The source (proxy) router must support Cisco IP SLA, or JUNIPER RPM, or at least DISMAN-PING-MIB.
    iSPI QA will use SNMP set requests with a set community string to trigger the ping on the source router/interface
    and get the result via SNMP read requests using the same Mib.

    Best regards,
    Sergey

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.