SonicWall Gen 7 - missing CPU graph / data

Help
1

Hi,
doeas anyone can help how to get CPU data for SonicWall Gen 7 firewall (in my case it is NSa 2700).
All others is working fine.

2

I don’t have any such devices, but some places to maybe start:

Do you have other sonicwall devices with working CPU graphs to compare against?
Can you post the discovery debug via pastebin? Device → 3 dots top right → Capture … https://p.libren.ms/

Looking at the code, it’s trying to get the CPU using:

.1.3.6.1.4.1.8741.1.3.1.3.0
(SONICWALL-FIREWALL-IP-STATISTICS-MIB::sonicCurrentCPUUtil.0)

-or-

{sysObjectID}.2.1.3.0
(get the result of 1.3.6.1.2.1.1.2 and add .2.1.3.0 to the end of it)

What happens when you manually snmpwalk those OIDs?

3

Hi,

Can you post the discovery debug via pastebin? → pastebin

snmpwalk:

snmpwalk -v2c -c community sonicwall_host .1.3.6.1.4.1.8741.1.3.1.3.0
iso.3.6.1.4.1.8741.1.3.1.3.0 = Gauge32: 43

snmpwalk -v2c -c community sonicwall_host .2.1.3.0
joint-iso-ccitt.1.3.0 = No more variables left in this MIB View (It is past the end of the MIB tree)

snmpwalk -v2c -c community sonicwall_host 1.3.6.1.2.1.1.2
iso.3.6.1.2.1.1.2.0 = OID: iso.0.3.0.6.0.1.0

4

I think these models have incomplete support and need more work.

In the debug, it’s hitting the bottom block (line 837):

SNMP['/usr/bin/snmpget' '-v2c' '-c' 'COMMUNITY' '-Ovq' '-M' '/opt/librenms/mibs:/opt/librenms/mibs/sonicwall' 'udp:HOSTNAME:161' '.1.0.3.0.6.0.1.0.2.1.3.0']

So what do you get from .1.0.3.0.6.0.1.0.2.1.3.0 - presuming nothing relevant?

You’re getting what looks like valid data on .1.3.6.1.4.1.8741.1.3.1.3.0 but the code as it’s written won’t use that as it expects the sysObjectID to be .1.3.6.1.4.1.8471.1 in LibreNMS/OS/Sonicwall.php

Will need others to tell us if they see this on their devices also and what other models do, would potentially need the logic to be altered in the code to account for it. For example in your case, checking the logic to match for .1.3.6.1.4.1.8741.1 -or- .1.0.3.0.6.0.1.0 would get it working.

I suspect from this, that the device doesn’t play by the original rules: Sonicwall Gen 7 OS - #3 by SegaMegaDave

The PR which responds to the above mentions CPU is not covered: Add Sonicwall OS 7 by edgetho007 · Pull Request #12997 · librenms/librenms · GitHub

5

So what do you get from .1.0.3.0.6.0.1.0.2.1.3.0 - presuming nothing relevant?

snmpwalk -v2c -c SNMPSTRING 192.168.1.1 1.0.3.0.6.0.1.0.2.1.3.0
iso.0.3.0.6.0.1.0.2.1.3.0 = No Such Object available on this agent at this OID

6

Hi,

new firmware release and now I can see CPU usage, but only as aggregate.
Is it possible to split it for every processor?

7

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.