Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

"No Data for this Entry" in Serial Interface Utilization Summary report

Description

The Serial Interface Utilization Summary report seems to find the interfaces properly, but where the RRD data should be display is simply "There is No Data for this Entry".

Acceptance / Success Criteria

None

Attachments

4
  • 23 Jul 2013, 12:21 PM
  • 22 Jul 2013, 06:51 PM
  • 22 Jul 2013, 03:32 PM
  • 13 Jun 2013, 12:06 PM

Lucidchart Diagrams

Activity

Show:

Alejandro Galue July 30, 2013 at 4:22 PM

The current report template is working as expected.

Alejandro Galue July 25, 2013 at 9:28 AM

Ravy,

You're welcome!

I'm glad to hear that it is working better now.

For the fxp0.0, the DB has 0 for the ifSpeed, and that's why the report is displaying 0.0 kbps for the speed.

opennms_juniper=# select snmpifindex,snmpifname,snmpifdescr,snmpphysaddr,snmpifspeed from snmpinterface where nodeid=5 and snmpcollect in ('C','UC'); snmpifindex | snmpifname | snmpifdescr | snmpphysaddr | snmpifspeed -------------+------------+-------------+--------------+------------- 16 | lo0.0 | lo0.0 | | 0 13 | fxp0.0 | fxp0.0 | 00a0a563c7d8 | 0 504 | ge-0/0/1.0 | ge-0/0/1.0 | 001f12dfb001 | 1000000000 502 | ge-0/0/0.0 | ge-0/0/0.0 | 001f12dfb000 | 1000000000 (4 rows)

You can validate the current value of the ifSpeed by executing the following command:

snmpwalk -v 2c -c xxxx 10.216.114.102 ifSpeed.13

Replace xxxx with the SNMP community string.

Ravi Prakash July 24, 2013 at 9:17 PM

Hi Alejandro

Thanks for your help , I do not see the issue with latest tests I ran so data looks good.

There is one other thing which we want to validate with you , For the same device junos-m10-1-space , fxp0.0 interface rate shows up as 0.0 kb/s where as interface rate is 100 mb. Can you check on that?

Alejandro Galue July 24, 2013 at 9:52 AM

Ravy,

Guess you forgot to attach the SerialInterfaceSummaryReport.pdf file

Here are some notes of my last tests:

I've installed the latest RPM snapshots for master on a CentOS 6 64-bits VM:

opennms-core-1.13.0-0.20130723.1.noarch
opennms-ncs-1.13.0-0.20130723.1.noarch
opennms-plugin-collector-juniper-tca-1.13.0-0.20130723.1.noarch
opennms-plugin-protocol-xml-1.13.0-0.20130723.1.noarch
opennms-repo-bleeding-1.0-18.noarch
opennms-repo-stable-1.0-18.noarch
opennms-webapp-jetty-1.13.0-0.20130723.1.noarch

Then I've configured OpenNMS to use the configuration files, the DB dump, and the JRBs you sent (with storeByGroup=true).

The graphs and the report are consistent and are displaying the correct data for the two interfaces in question on the node junos-m10-1-space.

Because the JRBs you sent contain data only for July 22th, I've generated the report to be consistent with that, I mean:
Report Time Range = 1
Report Start Date = 2013-07-22

It is possible for you to upgrade OpenNMS to use the latest RPMs ?

Ravi Prakash July 23, 2013 at 7:15 PM

Alejandro

I agree with your explanation and you are correct that report will only be generated for interfaces for which data is being collected and correct data is being generated in the report you have.
Howerver the report generated on the space server says no data for this entry for the ge-0/0/0.0 interface and ge-0/0/1.0 interface? Look at the attached SerialInterfaceSummaryReport.pdf and look for node junos-m10-1-space .
I will like to do a remote web meeting and show you what I see. Can we do a call or meeting today or tomorrow?

Cannot Reproduce

Details

Assignee

Reporter

Labels

Components

Fix versions

Affects versions

Priority

PagerDuty

Created November 2, 2012 at 2:01 PM
Updated January 27, 2017 at 4:20 PM
Resolved July 30, 2013 at 4:22 PM