PulseSecure appliances are not discovered #4680

Closed
pentium90 opened this Issue Sep 30, 2016 · 8 comments

Projects

None yet

4 participants

@pentium90

Hi librenms,

In includes/discovery/os/pulse.inc.php string for $sysDescr ('Pulse Connect Secure') is incorrect. Our Pulse devices will only be discovered after I changed string to only 'Pulse Secure', because SNMPv2-SMI::mib-2.1.1.0 returns:

sysDescr.0 = STRING: Pulse Secure, LLC,Pulse Connect Secure,VA-SPE,8.2R1 (build 41241)
sysDescr.0 = STRING: Pulse Secure,LLC,SA-2500,8.0R13 (build 38659)
sysDescr.0 = STRING: Pulse Secure,LLC,SA-6500,8.0R13 (build 38659)

There is also a newer MIB file for Pulse devices (REVISION "201607071610Z") - see attached files.

Version info:
[WARN] Your install is out of date: e17c34b (Thu, 29 Sep 2016 19:25:27 +0000)
[WARN] Your local git contains modified files, this could prevent automatic updates.
Modified files:
includes/discovery/os/pulse.inc.php
mibs/PULSESECURE-PSG-MIB
DB Schema: 140
PHP: 7.0.8-0ubuntu0.16.04.2
MySQL: 10.0.27-MariaDB-0ubuntu0.16.04.1
RRDTool: 1.5.5
SNMP: NET-SNMP version: 5.7.3

pulse.inc.php.txt
PULSESECURE-PSG-MIB.txt

Best regards

Stephan

DO NOT DELETE THIS INFORMATION.

Please read this information carefully.

  • Is your install up to date? Updating your install
    Please do not submit an issue if your install is not up to date within the last 24 hours or on a stable monthly release.
  • Please include all of the information between the ==================================== section of ./validate.php.
  • If you would like us to add a new device then please provide the information asked for here
  • Please provide as much detail as possible.
@Stalker71
Contributor

Hi Stephan,

When I created this module last year it worked on real device and on the virtual one.
So far, it still work for us in production. Maybe you have another version as Pulse was just another company out of Juniper. ;-)

So maybe the best way to fix it is to put a "or" instead or delete the old variable match.

@Rosiak Rosiak added a commit to Rosiak/librenms that referenced this issue Oct 1, 2016
@Rosiak Rosiak newdevice: Add support for more Pulse Secure devices #4680 67e95f1
@murrant
Contributor
murrant commented Oct 1, 2016

It would be great if you could post sysDescr and sysObjectID pairs so we can improve the tests.

@laf laf added the New-Device label Oct 1, 2016
@laf
Member
laf commented Oct 1, 2016

Please provide the info as requested in the issue template: http://docs.librenms.org/Support/FAQ/#faq20

@pentium90 pentium90 closed this Oct 4, 2016
@pentium90 pentium90 reopened this Oct 4, 2016
@laf
Member
laf commented Oct 5, 2016

Are all these different products? Do they do the same thing, same os? You need to give us a bit more info to work this out - I'm not a user of Pulse products nor do I know anything about them.

@pentium90
pentium90 commented Oct 5, 2016 edited

All of them are different variants of same product (Neoteris/Juniper/Pulse Secure client-to-site VPN gateway) with same OS (called IVE, a hardened Redhat) but different versions, running on different x86 hardware (RAM, CPU, HDD).
https://www.pulsesecure.net/base/images/kb-images/kb-files/techpubs/software/ive/guides/howtos/SA-IC-MAG-SNMP-Monitoring-Guide.pdf

@laf
Member
laf commented Oct 5, 2016

So we should be renaming this from pulse to ive then?

@pentium90

no, Pulse is ok, only the logo should be updated from Juniper to PulseSecure too:
https://media.licdn.com/mpr/mpr/shrink_200_200/AAEAAQAAAAAAAAQYAAAAJDczYzI4YTdjLWQxYzktNDlkOS1hZWZiLTA2OGExOWU4MjBlYg.png
but this is all just cosmetic: the issue is in "includes/discovery/os/pulse.inc.php" string for $sysDescr ('Pulse Connect Secure')

@laf laf closed this in #4689 Oct 6, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment