Skip to:

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

Problems in datacollection config for Juniper jrouters

Description

I've found that my Juniper SRX240 boxes reply to the OID defined in the juniper-jrouter group:

<group name="juniper-jrouter" ifType="ignore"> <mibObj oid=".1.3.6.1.4.1.2636.3.1.13.1.11.9.1.0" instance="0" alias="juniperMemUsed" type="gauge32" /> <mibObj oid=".1.3.6.1.4.1.2636.3.1.13.1.15.9.1.0" instance="0" alias="juniperMemInst" type="gauge32" /> <mibObj oid=".1.3.6.1.4.1.2636.3.1.13.1.7.9.1.0" instance="0" alias="juniperTempRe" type="gauge32" /> <mibObj oid=".1.3.6.1.4.1.2636.3.1.13.1.8.9.1.0" instance="0" alias="juniperCpuRe" type="gauge32" /> <mibObj oid=".1.3.6.1.4.1.2636.3.34.1.1" instance="0" alias="junFwddCpuMKernel" type="gauge32" /> <mibObj oid=".1.3.6.1.4.1.2636.3.34.1.2" instance="0" alias="junFwddCpuRtThread" type="gauge32" /> <mibObj oid=".1.3.6.1.4.1.2636.3.34.1.3" instance="0" alias="junFwddHeapUtiliz" type="gauge32" /> <mibObj oid=".1.3.6.1.4.1.2636.3.34.1.4" instance="0" alias="junFwddBufferUtiliz" type="gauge32" /> <mibObj oid=".1.3.6.1.4.1.2636.3.34.1.5" instance="0" alias="junFwddUptime" type="gauge32" /> </group>

The OID's starting with .1.3.6.1.4.1.2636.3.34 seem to relate to a fwwd process which is also available on my SRX240 boxes. Eg:

cyrille@node0-fwlou> show chassis hardware node0: -------------------------------------------------------------------------- Hardware inventory: Item Version Part number Serial number Description Chassis AG26xxxxx187 SRX240H Routing Engine REV 42 750-021793 AABxxxxx3 RE-SRX240H FPC 0 FPC PIC 0 16x GE Base PIC Power Supply 0 node1: -------------------------------------------------------------------------- Hardware inventory: Item Version Part number Serial number Description Chassis AG2xxxxx347 SRX240H Routing Engine REV 42 750-021793 Axxxxx96 RE-SRX240H FPC 0 FPC PIC 0 16x GE Base PIC Power Supply 0 {primary:node0} cyrille@node0-fwlou> show chassis firmware node0: -------------------------------------------------------------------------- Part Type Version FPC 0 O/S Version 12.1X44-D35.5 by builder on 2014-05 FWDD O/S Version 12.1X44-D35.5 by builder on 2014-05 node1: -------------------------------------------------------------------------- Part Type Version FPC 0 O/S Version 12.1X44-D35.5 by builder on 2014-05 FWDD O/S Version 12.1X44-D35.5 by builder on 2014-05 {primary:node0} cyrille@node0-fwlou> show pfe fwdd | last 10 Pfe (16) 0 17764 Pfe (29) 0 1 Pfe (47) 0 1 Dfw ( 6) 9 9 Dfw (18) 130 0 GenCfg ( 2) 470 0 GenCfg ( 6) 7991 0 GenCfg ( 8) 100 0 GenCfg ( 9) 4 0 STP ( 1) 34 34 {primary:node0} cyrille@node0-fwlou>

The OID's starting with .1.3.6.1.4.1.2636.3.1.13 relate to a table and seem to monitor only 1 specific line in this table. Why this line and not the pther ones? I think there's a problem here:

root@opennms:/home/support/JuniperMibs# snmptable -v 3 -a SHA -A xxxxxxxxxxxxxxxxx -x AES -X xxxxxxxxxxxxxxx -u opennms -l AuthPriv fwlou jnxOperatingTable SNMP table: JUNIPER-MIB::jnxOperatingTable jnxOperatingContentsIndex jnxOperatingL1Index jnxOperatingL2Index jnxOperatingL3Index jnxOperatingDescr jnxOperatingState jnxOperatingTemp jnxOperatingCPU jnxOperatingISR jnxOperatingDRAMSize jnxOperatingBuffer jnxOperatingHeap jnxOperatingUpTime jnxOperatingLastRestart jnxOperatingMemory jnxOperatingStateOrdered jnxOperatingChassisId jnxOperatingChassisDescr jnxOperatingRestartTime jnxOperating1MinLoadAvg jnxOperating5MinLoadAvg jnxOperating15MinLoadAvg 1 1 0 0 node0 midplane running 0 0 0 0 0 0 1701008400 0:0:00:00.00 0 running node0 node0 2014-12-23,12:21:20.0,+1:0 0 0 0 1 2 0 0 node1 midplane running 0 0 0 0 0 0 852605100 0:0:00:00.00 0 running node1 node1 2015-3-31,18:1:48.0,+2:0 0 0 0 2 1 0 0 node0 PEM 0 running 0 0 0 0 0 0 1701008651 0:0:00:00.00 0 running node0 node0 2014-12-23,12:21:20.0,+1:0 0 0 0 2 2 0 0 node1 PEM 0 running 0 0 0 0 0 0 852605348 0:0:00:00.00 0 running node1 node1 2015-3-31,18:1:48.0,+2:0 0 0 0 4 1 0 0 node0 SRX240 PowerSupply fan 1 running 0 0 0 0 0 0 852647415 0:0:00:00.00 0 running node0 node0 2015-3-31,17:54:52.0,+2:0 0 0 0 4 2 0 0 node0 SRX240 PowerSupply fan 2 running 0 0 0 0 0 0 852647415 0:0:00:00.00 0 running node0 node0 2015-3-31,17:54:52.0,+2:0 0 0 0 4 3 0 0 node0 SRX240 CPU fan 1 running 0 0 0 0 0 0 852647415 0:0:00:00.00 0 running node0 node0 2015-3-31,17:54:52.0,+2:0 0 0 0 4 4 0 0 node0 SRX240 CPU fan 2 running 0 0 0 0 0 0 852647413 0:0:00:00.00 0 running node0 node0 2015-3-31,17:54:52.0,+2:0 0 0 0 4 5 0 0 node0 SRX240 IO fan 1 running 0 0 0 0 0 0 852647414 0:0:00:00.00 0 running node0 node0 2015-3-31,17:54:52.0,+2:0 0 0 0 4 6 0 0 node0 SRX240 IO fan 2 running 0 0 0 0 0 0 852647414 0:0:00:00.00 0 running node0 node0 2015-3-31,17:54:52.0,+2:0 0 0 0 4 7 0 0 node1 SRX240 PowerSupply fan 1 running 0 0 0 0 0 0 852588967 0:0:00:00.00 0 running node1 node1 2015-3-31,18:4:31.0,+2:0 0 0 0 4 8 0 0 node1 SRX240 PowerSupply fan 2 running 0 0 0 0 0 0 852588971 0:0:00:00.00 0 running node1 node1 2015-3-31,18:4:31.0,+2:0 0 0 0 4 9 0 0 node1 SRX240 CPU fan 1 running 0 0 0 0 0 0 852588975 0:0:00:00.00 0 running node1 node1 2015-3-31,18:4:31.0,+2:0 0 0 0 4 10 0 0 node1 SRX240 CPU fan 2 running 0 0 0 0 0 0 852588978 0:0:00:00.00 0 running node1 node1 2015-3-31,18:4:31.0,+2:0 0 0 0 4 11 0 0 node1 SRX240 IO fan 1 running 0 0 0 0 0 0 852588982 0:0:00:00.00 0 running node1 node1 2015-3-31,18:4:31.0,+2:0 0 0 0 4 12 0 0 node1 SRX240 IO fan 2 running 0 0 0 0 0 0 852588986 0:0:00:00.00 0 running node1 node1 2015-3-31,18:4:31.0,+2:0 0 0 0 7 1 0 0 node0 FPC: FPC @ 0/*/* running 0 0 0 0 0 0 853495695 0:0:00:00.00 0 running node0 node0 2015-3-31,15:33:29.0,+2:0 0 0 0 7 6 0 0 node1 FPC: FPC @ 0/*/* running 0 0 0 0 0 0 852585180 0:0:10:49.27 0 running node1 node1 2015-3-31,18:5:9.0,+2:0 0 0 0 8 1 1 0 node0 PIC: 16x GE Base PIC @ 0/0/* running 0 0 0 0 0 0 1700985499 0:0:00:00.00 0 running node0 node0 2014-12-23,12:25:11.0,+1:0 0 0 0 8 6 1 0 node1 PIC: 16x GE Base PIC @ 0/0/* running 0 0 0 0 0 0 852585055 0:0:10:50.65 0 running node1 node1 2015-3-31,18:5:11.0,+2:0 0 0 0 9 1 0 0 node0 Routing Engine running 36 23 0 1073741824 78 0 1701008400 0:0:00:00.00 1024 running node0 node0 2014-12-23,12:21:20.0,+1:0 36 25 18 9 1 1 0 node0 USB Hub running 0 0 0 0 0 0 0 0:0:00:00.00 0 running node0 node0 0 0 0 9 2 0 0 node1 Routing Engine running 36 11 0 1073741824 68 0 852605100 0:0:00:00.00 1024 running node1 node1 2015-3-31,18:1:48.0,+2:0 5 6 5 9 2 1 0 node1 USB Hub running 0 0 0 0 0 0 0 0:0:00:00.00 0 running node1 node1 0 0 0 root@opennms:/home/support/JuniperMibs#

How should I fix it?

Cyrille

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Show:

Ronny Trommer July 15, 2015 at 7:25 PM

Cyrille Bollu July 15, 2015 at 3:53 AM

I'll create a new issue for the jnxOperatingTable problem.

So, you can already commit https://github.com/OpenNMS/opennms/pull/321 which shouldn't have adverse effects.

Cyrille Bollu July 14, 2015 at 10:32 AM

The problem with the jnxOperatingTable is that it is a table but it's not collected as a table at all (using ifType="ignore" rather than ifType="all").

I might be able to fix that, but that has some implication:

1- In my case the jnxOperatingTable contains about 20 rows which might fills up openNMS graphs. Lots of these rows might be filtered ou tough
2- fixing that might imply breaking previous collections as they will move from node-level colelction to a table-specific collection

Any thought?

Cyr

Cyrille Bollu July 14, 2015 at 10:14 AM

I've created a PR for fixing 2 of these problems: https://github.com/OpenNMS/opennms/pull/321

The problem related to the collection of data in the jnxOperatingTable is much more complicated and maybe deserves an issue on its own.

Cyr

Cyrille Bollu July 8, 2015 at 4:50 AM

There's a third problem: The "Juniper J-Routers" systemDef duplicates the includeGroup already defined in the (more generix) "Juniper Routers" systemDef:

<systemDef name="Juniper Routers">
<sysoidMask>.1.3.6.1.4.1.2636.1.</sysoidMask>
<collect>
<includeGroup>juniper-router</includeGroup>
<includeGroup>mib2-X-interfaces</includeGroup>
<includeGroup>mib2-X-interfaces-pkts</includeGroup>
<includeGroup>ietf-bgp4-peer-stats</includeGroup>
</collect>
</systemDef>

<systemDef name="Juniper J-Routers">
<sysoidMask>.1.3.6.1.4.1.2636.1.1.1.2.19</sysoidMask>
<collect>
<includeGroup>juniper-jrouter</includeGroup>
<includeGroup>mib2-X-interfaces</includeGroup>
<includeGroup>mib2-X-interfaces-pkts</includeGroup>
<includeGroup>ietf-bgp4-peer-stats</includeGroup>
</collect>
</systemDef>

There's no point on doing that; The "Juniper J-Routers" systemDef could just be:

<systemDef name="Juniper J-Routers">
<sysoidMask>.1.3.6.1.4.1.2636.1.1.1.2.19</sysoidMask>
<collect>
<includeGroup>juniper-jrouter</includeGroup>
</collect>
</systemDef>

Fixed

Details

Assignee

Reporter

Labels

Components

Fix versions

Affects versions

Priority

PagerDuty

Created July 8, 2015 at 4:42 AM
Updated June 3, 2019 at 7:08 AM
Resolved July 15, 2015 at 7:25 PM