We have a PSA-3000 running Connect Secure 9.1R8. We upgraded to 9.1R8 from 9.1R1 on 7/31. Prior to the upgrade all sensors and firewall data was being reported. After the upgrade it’s now showing as a generic linux server with no sensors. I assume the MIBs have changed or something is not reporting properly. Here are the discover, poller, snmpbulkwalk, and MIBs
discover.php
https://p.libren.ms/view/bd4b3a85
poller.php
https://p.libren.ms/view/56524247
snmpbulkwalk
https://p.libren.ms/view/aaa2240b
MIBs
https://p.libren.ms/view/92ece294
Thanks!
What probably changed is the sysobjectid.
Try adding the new one to the definition file for that OS. If that works, please push your changes to git
I have submitted PR 12066 to address this
OK on looking further in to this, PCS is presenting a generic linux SysObjectId value which means we can’t use that to match the device.
If you have a Pulse support account you can see the open issue here for this problem
We could potentially use these OID values to match PCS instead:
iso.3.6.1.4.1.12532.6.0 = STRING: "Pulse Connect Secure,PSA7000-V
"
Note that the value includes a newline, I’m not sure how to include that in the discovery config. Something like this may work:
discovery:
-
sysObjectID:
- .1.3.6.1.4.1.12532.
snmpget:
.1.3.6.1.4.1.12532.6:
- "Pulse Connect Secure,PSA7000-V\n"
- "Pulse Connect Secure,PSA5000-V\n"
- "Pulse Connect Secure,PSA3000-V\n"
This issue is fixed in PCS release 9.1R8.1 or later and PCS 9.1R9 when it gets released.
Pulse have updated their KB on the topic - fixed in 9.1R8 and later.
Probably better to update the device than try to patch LibreNMS for a broken implementation of SNMP.
https://kb.pulsesecure.net/articles/Pulse_Secure_Article/KB44533