Our vBulletin migration is complete.
Welcome vBulletin users! All content and user information from the Micro Focus Forums (vBulletin) site has been migrated to this site. READ MORE.
ramesh9 Acclaimed Contributor.
Acclaimed Contributor.
127 views

Ping Latency data collection not happening

Jump to solution

Hello All

 

NNM 9.2x on Linux

QA SPI with latest patch installed

NPS 9.2x on same box.

 

We had configured PingPair.conf and PingPairPoll.conf file as per QA SPI Online help document and we are able to see Ping Pair been configured in QA SPI menu in NNMi.

 

However the data for QA Ping Pair is not getting collected and if we check following folder,

 

/var/opt/OV/NNMPerformanceSPI/Ping_Latency/archives/metric

 

the metrics file is not listed.

 

Again the status of PingPair in QA SPI configuration shows as "No Status".

0 Likes
1 Solution

Accepted Solutions
Highlighted
Absent Member.. Walinton Absent Member..
Absent Member..

Re: Ping Latency data collection not happening

Jump to solution

Hello Ramesh

 

For this to work, the NNMi management server will need SNMP write access to the source router defined in the PingPair.conf file? Have this be completed?


Please find the source router on the NNMi map and then right click, choose Configuration Details > Communication Settings.  Does a valid Write community string appears as an option on this report?

 

In the Quality Assurance > Ping Latency Pairs view, When you look at this view, do you see both Source Name and Source IP as well as Destination IP and Destination Name defined?

 

Another possibility is that the configuration in the PingPairPolling.cfg file is incorrect, or with a very large value causing that the iSPI is not actually triggering the Ping Requests. Can you share the contents?

 

Also, as a test. Can you remove this file (PingPairPolling.cfg) and then

 

Restart the qajboss process (ovstop qajboss; ovstart qajboss) *** Changes to the PingPairPolling.conf require a restart of the qajboss process.

 

Run nmsqapingpairconfig.ovpl  -resyncConfig command again? So that the iSPI uses the default Polling Interval.

 

Regards,

 

 

 

 

 

HP Support
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.
2 Replies
Highlighted
Absent Member.. Walinton Absent Member..
Absent Member..

Re: Ping Latency data collection not happening

Jump to solution

Hello Ramesh

 

For this to work, the NNMi management server will need SNMP write access to the source router defined in the PingPair.conf file? Have this be completed?


Please find the source router on the NNMi map and then right click, choose Configuration Details > Communication Settings.  Does a valid Write community string appears as an option on this report?

 

In the Quality Assurance > Ping Latency Pairs view, When you look at this view, do you see both Source Name and Source IP as well as Destination IP and Destination Name defined?

 

Another possibility is that the configuration in the PingPairPolling.cfg file is incorrect, or with a very large value causing that the iSPI is not actually triggering the Ping Requests. Can you share the contents?

 

Also, as a test. Can you remove this file (PingPairPolling.cfg) and then

 

Restart the qajboss process (ovstop qajboss; ovstart qajboss) *** Changes to the PingPairPolling.conf require a restart of the qajboss process.

 

Run nmsqapingpairconfig.ovpl  -resyncConfig command again? So that the iSPI uses the default Polling Interval.

 

Regards,

 

 

 

 

 

HP Support
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.
ramesh9 Acclaimed Contributor.
Acclaimed Contributor.

Re: Ping Latency data collection not happening

Jump to solution

Hi Walinton

 

Thanks, we do not have write community access to the device from NNM and we believe that is the reason it fails.

 

Thanks

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.