New Junos Pulse not detected when updating to version 9.1R6
Hi,
We upgraded a Junos Pulse VPN box to a newer version and since the device is changed to a Linux Device. Our service provider contacted also Junos but they couldn't help they said in the first place. Anything you can do to help getting the right discovery again?
Versions of Observium running in production - Stable, in LAB latest CE.
Example upgrade of a device changing from Juiperive to Linux in our LAB 2020-07-17 14:31:43 nlhtc-gclab-hpsa1 Vendor changed: 'Pulse Secure' -> '' 2020-07-17 14:31:43 nlhtc-gclab-hpsa1 Hardware changed: 'Secure,PSA-3000' -> 'Generic' 2020-07-17 14:31:43 nlhtc-gclab-hpsa1 Version changed: '9.1R6' -> '' 2020-07-17 14:30:02 nlhtc-gclab-hpsa1 Mempools: 1 deleted, 4 unchanged. 2020-07-17 14:30:02 Memory pool removed: mib PULSESECURE-PSG-MIB, index 0, descr Memory 2020-07-17 14:30:02 nlhtc-gclab-hpsa1 Processors: 1 deleted, 5 unchanged. 2020-07-17 14:30:02 Processor removed: type iveCpuUtil index 0 descr CPU Utilization 2020-07-17 14:30:02 nlhtc-gclab-hpsa1 OS changed: juniperive -> linux 2020-07-17 14:26:43 nlhtc-gclab-hpsa1 Hardware changed: 'PSA-3000' -> 'Secure,PSA-3000' 2020-07-17 14:26:43 nlhtc-gclab-hpsa1 Version changed: '9.1R1' -> '9.1R6' 2020-07-17 14:26:43 nlhtc-gclab-hpsa1 sysDescr -> '' 2020-07-17 14:26:43 nlhtc-gclab-hpsa1 sysObjectID -> '.1.3.6.1.4.1.8072.3.2.10' 2020-07-17 14:26:43 nlhtc-gclab-hpsa1 snmpEngineID changed: 80001F888095475A3E33B6405D -> 80001F8880C6DAC55E2309125F (probably the device was replaced). The device will be rediscovered. 2020-07-17 14:26:43 nlhtc-gclab-hpsa1 Device rebooted: after 18m 59s (Uptime: 18m 59s, previous: 1 year, 35 days, 1h 53m 35s, used: hrSystemUptime) 2020-07-17 14:26:43 nlhtc-gclab-hpsa1 Device status changed to Up 2020-07-17 14:11:31 nlhtc-gclab-hpsa1 Device status changed to Down (snmp -> ping)
LAB box, not Working [root@nlhtc-gclab-mon observium]# snmpwalk -v3 -u Test -a SHA -A test0001 -l authNoPriv nlhtc-gclab-hpsa1.dtq.nl-htc01.nxp.com SNMPv2-MIB::sysDescr.0 = STRING: SNMPv2-MIB::sysObjectID.0 = OID: NET-SNMP-MIB::netSnmpAgentOIDs.10 DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (49097) 0:08:10.97 SNMPv2-MIB::sysContact.0 = STRING: Eugene Lee SNMPv2-MIB::sysName.0 = STRING: nlhtc-gclab-hpsa1 SNMPv2-MIB::sysLocation.0 = STRING: HTC038 TestLab SNMPv2-MIB::sysServices.0 = INTEGER: 72 SNMPv2-MIB::sysORLastChange.0 = Timeticks: (0) 0:00:00.00
Production box, Working [root@nlams01manp001v observium]# snmpwalk -c xx -v2c brcpqnwras001-int.br-cpq01.nxp.com SNMPv2-MIB::sysDescr.0 = STRING: Pulse Secure, LLC,Pulse Connect Secure,PSA-5000,8.3R7.1 (build 65025) SNMPv2-MIB::sysObjectID.0 = OID: SNMPv2-SMI::enterprises.12532.256.3.1 DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (572322868) 66 days, 5:47:08.68 SNMPv2-MIB::sysContact.0 = STRING: Global Connectivity Team SNMPv2-MIB::sysName.0 = STRING: brazil-ssl.nxp.com SNMPv2-MIB::sysLocation.0 = STRING: Campinas, Brazil SNMPv2-MIB::sysServices.0 = INTEGER: 72 SNMPv2-MIB::sysORLastChange.0 = Timeticks: (0) 0:00:00.00
Production box, not working - version 9.1R6 [root@nlams01manp001v observium]# snmpwalk -c xx -v2c demucnwras001-mgt.de-muc01.nxp.com SNMPv2-MIB::sysDescr.0 = STRING: SNMPv2-MIB::sysObjectID.0 = OID: NET-SNMP-MIB::netSnmpAgentOIDs.10 DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (312846981) 36 days, 5:01:09.81 SNMPv2-MIB::sysContact.0 = STRING: Global_Connectivity@nxp.com SNMPv2-MIB::sysName.0 = STRING: demucnwras001-mgt SNMPv2-MIB::sysLocation.0 = STRING: Munich, Germany SNMPv2-MIB::sysServices.0 = INTEGER: 72 SNMPv2-MIB::sysORLastChange.0 = Timeticks: (1) 0:00:00.01
Kind regards, Dennis
Hi Dennis,
We probably detect the PulseSecure part (it's not been Juniper for a while, right?) using the sysDescr. After your upgrade that is suddenly empty, which does seem like a bug?
The sysObjectId is .1.3.6.1.4.1.8072.3.2.10 which is not specific to Pulse but basically just says "This is Linux".
We should probably be able to detect if it's Pulse by polling another MIB variable - Mike probably has the best idea/solution for this :-)
Tom
On 7/18/2020 12:18 PM, Dennis Hutten via observium wrote:
Hi,
We upgraded a Junos Pulse VPN box to a newer version and since the device is changed to a Linux Device. Our service provider contacted also Junos but they couldn’t help they said in the first place.
Anything you can do to help getting the right discovery again?
Versions of Observium running in production – Stable, in LAB latest CE.
Example upgrade of a device changing from Juiperive to Linux in our LAB
2020-07-17 14:31:43 nlhtc-gclab-hpsa1 Vendor changed: 'Pulse Secure' -> ''
2020-07-17 14:31:43 nlhtc-gclab-hpsa1 Hardware changed: 'Secure,PSA-3000' -> 'Generic'
2020-07-17 14:31:43 nlhtc-gclab-hpsa1 Version changed: '9.1R6' -> ''
2020-07-17 14:30:02 nlhtc-gclab-hpsa1 Mempools: 1 deleted, 4 unchanged.
2020-07-17 14:30:02 Memory pool removed: mib PULSESECURE-PSG-MIB, index 0, descr Memory
2020-07-17 14:30:02 nlhtc-gclab-hpsa1 Processors: 1 deleted, 5 unchanged.
2020-07-17 14:30:02 Processor removed: type iveCpuUtil index 0 descr CPU Utilization
2020-07-17 14:30:02 nlhtc-gclab-hpsa1 OS changed: juniperive -> linux
2020-07-17 14:26:43 nlhtc-gclab-hpsa1 Hardware changed: 'PSA-3000' -> 'Secure,PSA-3000'
2020-07-17 14:26:43 nlhtc-gclab-hpsa1 Version changed: '9.1R1' -> '9.1R6'
2020-07-17 14:26:43 nlhtc-gclab-hpsa1 sysDescr -> ''
2020-07-17 14:26:43 nlhtc-gclab-hpsa1 sysObjectID -> '.1.3.6.1.4.1.8072.3.2.10'
2020-07-17 14:26:43 nlhtc-gclab-hpsa1 snmpEngineID changed: 80001F888095475A3E33B6405D -> 80001F8880C6DAC55E2309125F (probably the device was replaced). The device will be rediscovered.
2020-07-17 14:26:43 nlhtc-gclab-hpsa1 Device rebooted: after 18m 59s (Uptime: 18m 59s, previous: 1 year, 35 days, 1h 53m 35s, used: hrSystemUptime)
2020-07-17 14:26:43 nlhtc-gclab-hpsa1 Device status changed to Up
2020-07-17 14:11:31 nlhtc-gclab-hpsa1 Device status changed to Down (snmp -> ping)
LAB box, not Working
[root@nlhtc-gclab-mon observium]# snmpwalk -v3 -u Test -a SHA -A test0001 -l authNoPriv nlhtc-gclab-hpsa1.dtq.nl-htc01.nxp.com
SNMPv2-MIB::sysDescr.0 = STRING:
SNMPv2-MIB::sysObjectID.0 = OID: NET-SNMP-MIB::netSnmpAgentOIDs.10
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (49097) 0:08:10.97
SNMPv2-MIB::sysContact.0 = STRING: Eugene Lee
SNMPv2-MIB::sysName.0 = STRING: nlhtc-gclab-hpsa1
SNMPv2-MIB::sysLocation.0 = STRING: HTC038 TestLab
SNMPv2-MIB::sysServices.0 = INTEGER: 72
SNMPv2-MIB::sysORLastChange.0 = Timeticks: (0) 0:00:00.00
Production box, Working
[root@nlams01manp001v observium]# snmpwalk -c xx -v2c brcpqnwras001-int.br-cpq01.nxp.com
SNMPv2-MIB::sysDescr.0 = STRING: Pulse Secure, LLC,Pulse Connect Secure,PSA-5000,8.3R7.1 (build 65025)
SNMPv2-MIB::sysObjectID.0 = OID: SNMPv2-SMI::enterprises.12532.256.3.1
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (572322868) 66 days, 5:47:08.68
SNMPv2-MIB::sysContact.0 = STRING: Global Connectivity Team
SNMPv2-MIB::sysName.0 = STRING: brazil-ssl.nxp.com
SNMPv2-MIB::sysLocation.0 = STRING: Campinas, Brazil
SNMPv2-MIB::sysServices.0 = INTEGER: 72
SNMPv2-MIB::sysORLastChange.0 = Timeticks: (0) 0:00:00.00
Production box, not working – version 9.1R6
[root@nlams01manp001v observium]# snmpwalk -c xx -v2c demucnwras001-mgt.de-muc01.nxp.com
SNMPv2-MIB::sysDescr.0 = STRING:
SNMPv2-MIB::sysObjectID.0 = OID: NET-SNMP-MIB::netSnmpAgentOIDs.10
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (312846981) 36 days, 5:01:09.81
SNMPv2-MIB::sysContact.0 = STRING: Global_Connectivity@nxp.com
SNMPv2-MIB::sysName.0 = STRING: demucnwras001-mgt
SNMPv2-MIB::sysLocation.0 = STRING: Munich, Germany
SNMPv2-MIB::sysServices.0 = INTEGER: 72
SNMPv2-MIB::sysORLastChange.0 = Timeticks: (1) 0:00:00.01
Kind regards,
Dennis
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Hi Tom,
It is my first toughed too that the system description identifies it but if mike can confirm this it would be nice.
We will chase Pulse secure on getting the system description working again.
Dennis
On 18 Jul 2020, at 13:30, Tom Laermans via observium observium@observium.org wrote:
Caution: EXT Email
Hi Dennis,
We probably detect the PulseSecure part (it's not been Juniper for a while, right?) using the sysDescr. After your upgrade that is suddenly empty, which does seem like a bug?
The sysObjectId is .1.3.6.1.4.1.8072.3.2.10 which is not specific to Pulse but basically just says "This is Linux".
We should probably be able to detect if it's Pulse by polling another MIB variable - Mike probably has the best idea/solution for this :-)
Tom
On 7/18/2020 12:18 PM, Dennis Hutten via observium wrote: Hi,
We upgraded a Junos Pulse VPN box to a newer version and since the device is changed to a Linux Device. Our service provider contacted also Junos but they couldn’t help they said in the first place. Anything you can do to help getting the right discovery again?
Versions of Observium running in production – Stable, in LAB latest CE.
Example upgrade of a device changing from Juiperive to Linux in our LAB 2020-07-17 14:31:43 nlhtc-gclab-hpsa1 Vendor changed: 'Pulse Secure' -> '' 2020-07-17 14:31:43 nlhtc-gclab-hpsa1 Hardware changed: 'Secure,PSA-3000' -> 'Generic' 2020-07-17 14:31:43 nlhtc-gclab-hpsa1 Version changed: '9.1R6' -> '' 2020-07-17 14:30:02 nlhtc-gclab-hpsa1 Mempools: 1 deleted, 4 unchanged. 2020-07-17 14:30:02 Memory pool removed: mib PULSESECURE-PSG-MIB, index 0, descr Memory 2020-07-17 14:30:02 nlhtc-gclab-hpsa1 Processors: 1 deleted, 5 unchanged. 2020-07-17 14:30:02 Processor removed: type iveCpuUtil index 0 descr CPU Utilization 2020-07-17 14:30:02 nlhtc-gclab-hpsa1 OS changed: juniperive -> linux 2020-07-17 14:26:43 nlhtc-gclab-hpsa1 Hardware changed: 'PSA-3000' -> 'Secure,PSA-3000' 2020-07-17 14:26:43 nlhtc-gclab-hpsa1 Version changed: '9.1R1' -> '9.1R6' 2020-07-17 14:26:43 nlhtc-gclab-hpsa1 sysDescr -> '' 2020-07-17 14:26:43 nlhtc-gclab-hpsa1 sysObjectID -> '.1.3.6.1.4.1.8072.3.2.10' 2020-07-17 14:26:43 nlhtc-gclab-hpsa1 snmpEngineID changed: 80001F888095475A3E33B6405D -> 80001F8880C6DAC55E2309125F (probably the device was replaced). The device will be rediscovered. 2020-07-17 14:26:43 nlhtc-gclab-hpsa1 Device rebooted: after 18m 59s (Uptime: 18m 59s, previous: 1 year, 35 days, 1h 53m 35s, used: hrSystemUptime) 2020-07-17 14:26:43 nlhtc-gclab-hpsa1 Device status changed to Up 2020-07-17 14:11:31 nlhtc-gclab-hpsa1 Device status changed to Down (snmp -> ping)
LAB box, not Working [root@nlhtc-gclab-mon observium]# snmpwalk -v3 -u Test -a SHA -A test0001 -l authNoPriv nlhtc-gclab-hpsa1.dtq.nl-htc01.nxp.com SNMPv2-MIB::sysDescr.0 = STRING: SNMPv2-MIB::sysObjectID.0 = OID: NET-SNMP-MIB::netSnmpAgentOIDs.10 DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (49097) 0:08:10.97 SNMPv2-MIB::sysContact.0 = STRING: Eugene Lee SNMPv2-MIB::sysName.0 = STRING: nlhtc-gclab-hpsa1 SNMPv2-MIB::sysLocation.0 = STRING: HTC038 TestLab SNMPv2-MIB::sysServices.0 = INTEGER: 72 SNMPv2-MIB::sysORLastChange.0 = Timeticks: (0) 0:00:00.00
Production box, Working [root@nlams01manp001v observium]# snmpwalk -c xx -v2c brcpqnwras001-int.br-cpq01.nxp.com SNMPv2-MIB::sysDescr.0 = STRING: Pulse Secure, LLC,Pulse Connect Secure,PSA-5000,8.3R7.1 (build 65025) SNMPv2-MIB::sysObjectID.0 = OID: SNMPv2-SMI::enterprises.12532.256.3.1 DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (572322868) 66 days, 5:47:08.68 SNMPv2-MIB::sysContact.0 = STRING: Global Connectivity Team SNMPv2-MIB::sysName.0 = STRING: brazil-ssl.nxp.com SNMPv2-MIB::sysLocation.0 = STRING: Campinas, Brazil SNMPv2-MIB::sysServices.0 = INTEGER: 72 SNMPv2-MIB::sysORLastChange.0 = Timeticks: (0) 0:00:00.00
Production box, not working – version 9.1R6 [root@nlams01manp001v observium]# snmpwalk -c xx -v2c demucnwras001-mgt.de-muc01.nxp.com SNMPv2-MIB::sysDescr.0 = STRING: SNMPv2-MIB::sysObjectID.0 = OID: NET-SNMP-MIB::netSnmpAgentOIDs.10 DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (312846981) 36 days, 5:01:09.81 SNMPv2-MIB::sysContact.0 = STRING: Global_Connectivity@nxp.commailto:Global_Connectivity@nxp.com SNMPv2-MIB::sysName.0 = STRING: demucnwras001-mgt SNMPv2-MIB::sysLocation.0 = STRING: Munich, Germany SNMPv2-MIB::sysServices.0 = INTEGER: 72 SNMPv2-MIB::sysORLastChange.0 = Timeticks: (1) 0:00:00.01
Kind regards, Dennis
_______________________________________________ observium mailing list observium@observium.orgmailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observiumhttps://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fpostman.memetic.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fobservium&data=02%7C01%7Cdennis.hutten%40nxp.com%7C76766cf5345a4fb75b0d08d82b0de8f2%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C637306686035996195&sdata=nBWgXffmbxFYYp2Z7RjZ5034ZDAiFaELu8MpxrN96Gg%3D&reserved=0
_______________________________________________ observium mailing list observium@observium.org https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fpostman.mem...
Small update. Pulse officially published a KB and recognized the bug.
https://kb.pulsesecure.net/articles/Pulse_Secure_Article/KB44533https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fkb.pulsesecure.net%2Farticles%2FPulse_Secure_Article%2FKB44533&data=02%7C01%7Cdennis.hutten%40nxp.com%7C5167447383f04f4ea3be08d82c801d99%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C637308276057617369&sdata=Qz6a9TG5U4IVwWSMcGs6zQc%2B%2BtCGGcMsiNsq8rGWL9o%3D&reserved=0
My question for now is if we can manual manipulate the autodiscovery or a second identifier can be used for the autodiscovery? This way it will keep working with the pulse mibs.
Kind regards, Dennis
On 20 Jul 2020, at 09:29, Dennis Hutten via observium observium@observium.org wrote:
Caution: EXT Email
Hi Tom,
It is my first toughed too that the system description identifies it but if mike can confirm this it would be nice.
We will chase Pulse secure on getting the system description working again.
Dennis
On 18 Jul 2020, at 13:30, Tom Laermans via observium observium@observium.org wrote:
Caution: EXT Email
Hi Dennis,
We probably detect the PulseSecure part (it's not been Juniper for a while, right?) using the sysDescr. After your upgrade that is suddenly empty, which does seem like a bug?
The sysObjectId is .1.3.6.1.4.1.8072.3.2.10 which is not specific to Pulse but basically just says "This is Linux".
We should probably be able to detect if it's Pulse by polling another MIB variable - Mike probably has the best idea/solution for this :-)
Tom
On 7/18/2020 12:18 PM, Dennis Hutten via observium wrote: Hi,
We upgraded a Junos Pulse VPN box to a newer version and since the device is changed to a Linux Device. Our service provider contacted also Junos but they couldn’t help they said in the first place. Anything you can do to help getting the right discovery again?
Versions of Observium running in production – Stable, in LAB latest CE.
Example upgrade of a device changing from Juiperive to Linux in our LAB 2020-07-17 14:31:43 nlhtc-gclab-hpsa1 Vendor changed: 'Pulse Secure' -> '' 2020-07-17 14:31:43 nlhtc-gclab-hpsa1 Hardware changed: 'Secure,PSA-3000' -> 'Generic' 2020-07-17 14:31:43 nlhtc-gclab-hpsa1 Version changed: '9.1R6' -> '' 2020-07-17 14:30:02 nlhtc-gclab-hpsa1 Mempools: 1 deleted, 4 unchanged. 2020-07-17 14:30:02 Memory pool removed: mib PULSESECURE-PSG-MIB, index 0, descr Memory 2020-07-17 14:30:02 nlhtc-gclab-hpsa1 Processors: 1 deleted, 5 unchanged. 2020-07-17 14:30:02 Processor removed: type iveCpuUtil index 0 descr CPU Utilization 2020-07-17 14:30:02 nlhtc-gclab-hpsa1 OS changed: juniperive -> linux 2020-07-17 14:26:43 nlhtc-gclab-hpsa1 Hardware changed: 'PSA-3000' -> 'Secure,PSA-3000' 2020-07-17 14:26:43 nlhtc-gclab-hpsa1 Version changed: '9.1R1' -> '9.1R6' 2020-07-17 14:26:43 nlhtc-gclab-hpsa1 sysDescr -> '' 2020-07-17 14:26:43 nlhtc-gclab-hpsa1 sysObjectID -> '.1.3.6.1.4.1.8072.3.2.10' 2020-07-17 14:26:43 nlhtc-gclab-hpsa1 snmpEngineID changed: 80001F888095475A3E33B6405D -> 80001F8880C6DAC55E2309125F (probably the device was replaced). The device will be rediscovered. 2020-07-17 14:26:43 nlhtc-gclab-hpsa1 Device rebooted: after 18m 59s (Uptime: 18m 59s, previous: 1 year, 35 days, 1h 53m 35s, used: hrSystemUptime) 2020-07-17 14:26:43 nlhtc-gclab-hpsa1 Device status changed to Up 2020-07-17 14:11:31 nlhtc-gclab-hpsa1 Device status changed to Down (snmp -> ping)
LAB box, not Working [root@nlhtc-gclab-mon observium]# snmpwalk -v3 -u Test -a SHA -A test0001 -l authNoPriv nlhtc-gclab-hpsa1.dtq.nl-htc01.nxp.com SNMPv2-MIB::sysDescr.0 = STRING: SNMPv2-MIB::sysObjectID.0 = OID: NET-SNMP-MIB::netSnmpAgentOIDs.10 DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (49097) 0:08:10.97 SNMPv2-MIB::sysContact.0 = STRING: Eugene Lee SNMPv2-MIB::sysName.0 = STRING: nlhtc-gclab-hpsa1 SNMPv2-MIB::sysLocation.0 = STRING: HTC038 TestLab SNMPv2-MIB::sysServices.0 = INTEGER: 72 SNMPv2-MIB::sysORLastChange.0 = Timeticks: (0) 0:00:00.00
Production box, Working [root@nlams01manp001v observium]# snmpwalk -c xx -v2c brcpqnwras001-int.br-cpq01.nxp.com SNMPv2-MIB::sysDescr.0 = STRING: Pulse Secure, LLC,Pulse Connect Secure,PSA-5000,8.3R7.1 (build 65025) SNMPv2-MIB::sysObjectID.0 = OID: SNMPv2-SMI::enterprises.12532.256.3.1 DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (572322868) 66 days, 5:47:08.68 SNMPv2-MIB::sysContact.0 = STRING: Global Connectivity Team SNMPv2-MIB::sysName.0 = STRING: brazil-ssl.nxp.com SNMPv2-MIB::sysLocation.0 = STRING: Campinas, Brazil SNMPv2-MIB::sysServices.0 = INTEGER: 72 SNMPv2-MIB::sysORLastChange.0 = Timeticks: (0) 0:00:00.00
Production box, not working – version 9.1R6 [root@nlams01manp001v observium]# snmpwalk -c xx -v2c demucnwras001-mgt.de-muc01.nxp.com SNMPv2-MIB::sysDescr.0 = STRING: SNMPv2-MIB::sysObjectID.0 = OID: NET-SNMP-MIB::netSnmpAgentOIDs.10 DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (312846981) 36 days, 5:01:09.81 SNMPv2-MIB::sysContact.0 = STRING: Global_Connectivity@nxp.commailto:Global_Connectivity@nxp.com SNMPv2-MIB::sysName.0 = STRING: demucnwras001-mgt SNMPv2-MIB::sysLocation.0 = STRING: Munich, Germany SNMPv2-MIB::sysServices.0 = INTEGER: 72 SNMPv2-MIB::sysORLastChange.0 = Timeticks: (1) 0:00:00.01
Kind regards, Dennis
_______________________________________________ observium mailing list observium@observium.orgmailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observiumhttps://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fpostman.memetic.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fobservium&data=02%7C01%7Cdennis.hutten%40nxp.com%7Ce7ffa339dbeb493e1f3108d82c7e9e5e%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C637308269619224604&sdata=zf91dqZDRFbmkgPhSPN%2FVd4DWUajjukOS0YWAyKI4vk%3D&reserved=0
_______________________________________________ observium mailing list observium@observium.org https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fpostman.mem... _______________________________________________ observium mailing list observium@observium.org https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fpostman.mem...
Hi,
please make and attach full snmp walk for device (with latest firmware):
snmpwalk -v2c -c <community> --hexOutputLength=0 -ObentxU <hostname> .1
myagent.snmpwalk snmpwalk -v2c -c <community> --hexOutputLength=0
-ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk
Dennis Hutten via observium wrote on 20.07.2020 10:49:
Small update. Pulse officially published a KB and recognized the bug.
https://kb.pulsesecure.net/articles/Pulse_Secure_Article/KB44533 https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fkb.pulsesecure.net%2Farticles%2FPulse_Secure_Article%2FKB44533&data=02%7C01%7Cdennis.hutten%40nxp.com%7C5167447383f04f4ea3be08d82c801d99%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C637308276057617369&sdata=Qz6a9TG5U4IVwWSMcGs6zQc%2B%2BtCGGcMsiNsq8rGWL9o%3D&reserved=0
My question for now is if we can manual manipulate the autodiscovery or a second identifier can be used for the autodiscovery? This way it will keep working with the pulse mibs.
Kind regards, Dennis
On 20 Jul 2020, at 09:29, Dennis Hutten via observium observium@observium.org wrote:
Caution: EXT Email
Hi Tom,
It is my first toughed too that the system description identifies it but if mike can confirm this it would be nice.
We will chase Pulse secure on getting the system description working again.
Dennis
On 18 Jul 2020, at 13:30, Tom Laermans via observium observium@observium.org wrote:
Caution: EXT Email
Hi Dennis,
We probably detect the PulseSecure part (it's not been Juniper for a while, right?) using the sysDescr. After your upgrade that is suddenly empty, which does seem like a bug?
The sysObjectId is .1.3.6.1.4.1.8072.3.2.10 which is not specific to Pulse but basically just says "This is Linux".
We should probably be able to detect if it's Pulse by polling another MIB variable - Mike probably has the best idea/solution for this :-)
Tom
On 7/18/2020 12:18 PM, Dennis Hutten via observium wrote:
Hi,
We upgraded a Junos Pulse VPN box to a newer version and since the device is changed to a Linux Device. Our service provider contacted also Junos but they couldn’t help they said in the first place.
Anything you can do to help getting the right discovery again?
Versions of Observium running in production – Stable, in LAB latest CE.
Example upgrade of a device changing from Juiperive to Linux in our LAB
2020-07-17 14:31:43 nlhtc-gclab-hpsa1 Vendor changed: 'Pulse Secure' -> ''
2020-07-17 14:31:43 nlhtc-gclab-hpsa1 Hardware changed: 'Secure,PSA-3000' -> 'Generic'
2020-07-17 14:31:43 nlhtc-gclab-hpsa1 Version changed: '9.1R6' -> ''
2020-07-17 14:30:02 nlhtc-gclab-hpsa1 Mempools: 1 deleted, 4 unchanged.
2020-07-17 14:30:02 Memory pool removed: mib PULSESECURE-PSG-MIB, index 0, descr Memory
2020-07-17 14:30:02 nlhtc-gclab-hpsa1 Processors: 1 deleted, 5 unchanged.
2020-07-17 14:30:02 Processor removed: type iveCpuUtil index 0 descr CPU Utilization
2020-07-17 14:30:02 nlhtc-gclab-hpsa1 OS changed: juniperive -> linux
2020-07-17 14:26:43 nlhtc-gclab-hpsa1 Hardware changed: 'PSA-3000' -> 'Secure,PSA-3000'
2020-07-17 14:26:43 nlhtc-gclab-hpsa1 Version changed: '9.1R1' -> '9.1R6'
2020-07-17 14:26:43 nlhtc-gclab-hpsa1 sysDescr -> ''
2020-07-17 14:26:43 nlhtc-gclab-hpsa1 sysObjectID -> '.1.3.6.1.4.1.8072.3.2.10'
2020-07-17 14:26:43 nlhtc-gclab-hpsa1 snmpEngineID changed: 80001F888095475A3E33B6405D -> 80001F8880C6DAC55E2309125F (probably the device was replaced). The device will be rediscovered.
2020-07-17 14:26:43 nlhtc-gclab-hpsa1 Device rebooted: after 18m 59s (Uptime: 18m 59s, previous: 1 year, 35 days, 1h 53m 35s, used: hrSystemUptime)
2020-07-17 14:26:43 nlhtc-gclab-hpsa1 Device status changed to Up
2020-07-17 14:11:31 nlhtc-gclab-hpsa1 Device status changed to Down (snmp -> ping)
LAB box, not Working
[root@nlhtc-gclab-mon observium]# snmpwalk -v3 -u Test -a SHA -A test0001 -l authNoPriv nlhtc-gclab-hpsa1.dtq.nl-htc01.nxp.com
SNMPv2-MIB::sysDescr.0 = STRING:
SNMPv2-MIB::sysObjectID.0 = OID: NET-SNMP-MIB::netSnmpAgentOIDs.10
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (49097) 0:08:10.97
SNMPv2-MIB::sysContact.0 = STRING: Eugene Lee
SNMPv2-MIB::sysName.0 = STRING: nlhtc-gclab-hpsa1
SNMPv2-MIB::sysLocation.0 = STRING: HTC038 TestLab
SNMPv2-MIB::sysServices.0 = INTEGER: 72
SNMPv2-MIB::sysORLastChange.0 = Timeticks: (0) 0:00:00.00
Production box, Working
[root@nlams01manp001v observium]# snmpwalk -c xx -v2c brcpqnwras001-int.br-cpq01.nxp.com
SNMPv2-MIB::sysDescr.0 = STRING: Pulse Secure, LLC,Pulse Connect Secure,PSA-5000,8.3R7.1 (build 65025)
SNMPv2-MIB::sysObjectID.0 = OID: SNMPv2-SMI::enterprises.12532.256.3.1
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (572322868) 66 days, 5:47:08.68
SNMPv2-MIB::sysContact.0 = STRING: Global Connectivity Team
SNMPv2-MIB::sysName.0 = STRING: brazil-ssl.nxp.com
SNMPv2-MIB::sysLocation.0 = STRING: Campinas, Brazil
SNMPv2-MIB::sysServices.0 = INTEGER: 72
SNMPv2-MIB::sysORLastChange.0 = Timeticks: (0) 0:00:00.00
Production box, not working – version 9.1R6
[root@nlams01manp001v observium]# snmpwalk -c xx -v2c demucnwras001-mgt.de-muc01.nxp.com
SNMPv2-MIB::sysDescr.0 = STRING:
SNMPv2-MIB::sysObjectID.0 = OID: NET-SNMP-MIB::netSnmpAgentOIDs.10
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (312846981) 36 days, 5:01:09.81
SNMPv2-MIB::sysContact.0 = STRING: Global_Connectivity@nxp.com
SNMPv2-MIB::sysName.0 = STRING: demucnwras001-mgt
SNMPv2-MIB::sysLocation.0 = STRING: Munich, Germany
SNMPv2-MIB::sysServices.0 = INTEGER: 72
SNMPv2-MIB::sysORLastChange.0 = Timeticks: (1) 0:00:00.01
Kind regards,
Dennis
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fpostman.mem...
observium mailing list observium@observium.org https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fpostman.mem...
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Hi Mike,
Find attached.
Kind regards, Dennis
From: Mike Stupalov mike@stupalov.ru On Behalf Of Mike Stupalov Sent: vrijdag 24 juli 2020 16:14 To: Observium observium@observium.org; Dennis Hutten via observium observium@observium.org Cc: Dennis Hutten dennis.hutten@nxp.com Subject: Re: [Observium] [EXT] Re: New Junos Pulse not detected when updating to version 9.1R6
Caution: EXT Email Hi,
please make and attach full snmp walk for device (with latest firmware):
snmpwalk -v2c -c <community> --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk
snmpwalk -v2c -c <community> --hexOutputLength=0 -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk
Dennis Hutten via observium wrote on 20.07.2020 10:49:
Small update. Pulse officially published a KB and recognized the bug.
https://kb.pulsesecure.net/articles/Pulse_Secure_Article/KB44533https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fkb.pulsesecure.net%2Farticles%2FPulse_Secure_Article%2FKB44533&data=02%7C01%7Cdennis.hutten%40nxp.com%7Cb220686214294286906708d82fdbd40f%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C637311968487302684&sdata=la4ubNKJI9XbW92BEFOTOTHRS7lZCy%2B8%2F9Z1D5dogVE%3D&reserved=0
My question for now is if we can manual manipulate the autodiscovery or a second identifier can be used for the autodiscovery? This way it will keep working with the pulse mibs.
Kind regards, Dennis
On 20 Jul 2020, at 09:29, Dennis Hutten via observium observium@observium.orgmailto:observium@observium.org wrote:
Caution: EXT Email Hi Tom,
It is my first toughed too that the system description identifies it but if mike can confirm this it would be nice.
We will chase Pulse secure on getting the system description working again. Dennis
On 18 Jul 2020, at 13:30, Tom Laermans via observium observium@observium.orgmailto:observium@observium.org wrote:
Caution: EXT Email Hi Dennis,
We probably detect the PulseSecure part (it's not been Juniper for a while, right?) using the sysDescr. After your upgrade that is suddenly empty, which does seem like a bug?
The sysObjectId is .1.3.6.1.4.1.8072.3.2.10 which is not specific to Pulse but basically just says "This is Linux".
We should probably be able to detect if it's Pulse by polling another MIB variable - Mike probably has the best idea/solution for this :-)
Tom
On 7/18/2020 12:18 PM, Dennis Hutten via observium wrote: Hi,
We upgraded a Junos Pulse VPN box to a newer version and since the device is changed to a Linux Device. Our service provider contacted also Junos but they couldn’t help they said in the first place. Anything you can do to help getting the right discovery again?
Versions of Observium running in production – Stable, in LAB latest CE.
Example upgrade of a device changing from Juiperive to Linux in our LAB 2020-07-17 14:31:43 nlhtc-gclab-hpsa1 Vendor changed: 'Pulse Secure' -> '' 2020-07-17 14:31:43 nlhtc-gclab-hpsa1 Hardware changed: 'Secure,PSA-3000' -> 'Generic' 2020-07-17 14:31:43 nlhtc-gclab-hpsa1 Version changed: '9.1R6' -> '' 2020-07-17 14:30:02 nlhtc-gclab-hpsa1 Mempools: 1 deleted, 4 unchanged. 2020-07-17 14:30:02 Memory pool removed: mib PULSESECURE-PSG-MIB, index 0, descr Memory 2020-07-17 14:30:02 nlhtc-gclab-hpsa1 Processors: 1 deleted, 5 unchanged. 2020-07-17 14:30:02 Processor removed: type iveCpuUtil index 0 descr CPU Utilization 2020-07-17 14:30:02 nlhtc-gclab-hpsa1 OS changed: juniperive -> linux 2020-07-17 14:26:43 nlhtc-gclab-hpsa1 Hardware changed: 'PSA-3000' -> 'Secure,PSA-3000' 2020-07-17 14:26:43 nlhtc-gclab-hpsa1 Version changed: '9.1R1' -> '9.1R6' 2020-07-17 14:26:43 nlhtc-gclab-hpsa1 sysDescr -> '' 2020-07-17 14:26:43 nlhtc-gclab-hpsa1 sysObjectID -> '.1.3.6.1.4.1.8072.3.2.10' 2020-07-17 14:26:43 nlhtc-gclab-hpsa1 snmpEngineID changed: 80001F888095475A3E33B6405D -> 80001F8880C6DAC55E2309125F (probably the device was replaced). The device will be rediscovered. 2020-07-17 14:26:43 nlhtc-gclab-hpsa1 Device rebooted: after 18m 59s (Uptime: 18m 59s, previous: 1 year, 35 days, 1h 53m 35s, used: hrSystemUptime) 2020-07-17 14:26:43 nlhtc-gclab-hpsa1 Device status changed to Up 2020-07-17 14:11:31 nlhtc-gclab-hpsa1 Device status changed to Down (snmp -> ping)
LAB box, not Working [root@nlhtc-gclab-mon observium]# snmpwalk -v3 -u Test -a SHA -A test0001 -l authNoPriv nlhtc-gclab-hpsa1.dtq.nl-htc01.nxp.com SNMPv2-MIB::sysDescr.0 = STRING: SNMPv2-MIB::sysObjectID.0 = OID: NET-SNMP-MIB::netSnmpAgentOIDs.10 DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (49097) 0:08:10.97 SNMPv2-MIB::sysContact.0 = STRING: Eugene Lee SNMPv2-MIB::sysName.0 = STRING: nlhtc-gclab-hpsa1 SNMPv2-MIB::sysLocation.0 = STRING: HTC038 TestLab SNMPv2-MIB::sysServices.0 = INTEGER: 72 SNMPv2-MIB::sysORLastChange.0 = Timeticks: (0) 0:00:00.00
Production box, Working [root@nlams01manp001v observium]# snmpwalk -c xx -v2c brcpqnwras001-int.br-cpq01.nxp.com SNMPv2-MIB::sysDescr.0 = STRING: Pulse Secure, LLC,Pulse Connect Secure,PSA-5000,8.3R7.1 (build 65025) SNMPv2-MIB::sysObjectID.0 = OID: SNMPv2-SMI::enterprises.12532.256.3.1 DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (572322868) 66 days, 5:47:08.68 SNMPv2-MIB::sysContact.0 = STRING: Global Connectivity Team SNMPv2-MIB::sysName.0 = STRING: brazil-ssl.nxp.com SNMPv2-MIB::sysLocation.0 = STRING: Campinas, Brazil SNMPv2-MIB::sysServices.0 = INTEGER: 72 SNMPv2-MIB::sysORLastChange.0 = Timeticks: (0) 0:00:00.00
Production box, not working – version 9.1R6 [root@nlams01manp001v observium]# snmpwalk -c xx -v2c demucnwras001-mgt.de-muc01.nxp.com SNMPv2-MIB::sysDescr.0 = STRING: SNMPv2-MIB::sysObjectID.0 = OID: NET-SNMP-MIB::netSnmpAgentOIDs.10 DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (312846981) 36 days, 5:01:09.81 SNMPv2-MIB::sysContact.0 = STRING: Global_Connectivity@nxp.commailto:Global_Connectivity@nxp.com SNMPv2-MIB::sysName.0 = STRING: demucnwras001-mgt SNMPv2-MIB::sysLocation.0 = STRING: Munich, Germany SNMPv2-MIB::sysServices.0 = INTEGER: 72 SNMPv2-MIB::sysORLastChange.0 = Timeticks: (1) 0:00:00.01
Kind regards, Dennis
_______________________________________________
observium mailing list
observium@observium.orgmailto:observium@observium.org
http://postman.memetic.org/cgi-bin/mailman/listinfo/observiumhttps://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fpostman.memetic.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fobservium&data=02%7C01%7Cdennis.hutten%40nxp.com%7Cb220686214294286906708d82fdbd40f%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C637311968487312680&sdata=jh0K9dUgyrn3gMrpo9GGo411SNgUWWc4wq%2FnLXwvBGY%3D&reserved=0
_______________________________________________ observium mailing list observium@observium.orgmailto:observium@observium.org https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fpostman.mem...https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fpostman.memetic.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fobservium&data=02%7C01%7Cdennis.hutten%40nxp.com%7Cb220686214294286906708d82fdbd40f%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C637311968487322675&sdata=hH11VCR4WREFNz8kH%2BXmo%2BgOKQr3yRvgpr4BqCnhqhM%3D&reserved=0 _______________________________________________ observium mailing list observium@observium.orgmailto:observium@observium.org https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fpostman.mem...https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fpostman.memetic.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fobservium&data=02%7C01%7Cdennis.hutten%40nxp.com%7Cb220686214294286906708d82fdbd40f%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C637311968487322675&sdata=hH11VCR4WREFNz8kH%2BXmo%2BgOKQr3yRvgpr4BqCnhqhM%3D&reserved=0
_______________________________________________
observium mailing list
observium@observium.orgmailto:observium@observium.org
http://postman.memetic.org/cgi-bin/mailman/listinfo/observiumhttps://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fpostman.memetic.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fobservium&data=02%7C01%7Cdennis.hutten%40nxp.com%7Cb220686214294286906708d82fdbd40f%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C637311968487332668&sdata=dlRJof9mswNb%2Bbed%2B56mvfKB4nZXwpa3JMLYnIveTm8%3D&reserved=0
-- Mike Stupalov Observium Limited, http://observium.orghttps://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fobservium.org%2F&data=02%7C01%7Cdennis.hutten%40nxp.com%7Cb220686214294286906708d82fdbd40f%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C637311968487332668&sdata=5WJMzfgP45pWGJPBTGicXYh1uwEeF8batSFOTgE42Yo%3D&reserved=0
Additionally fetch from device Private MIB file as described here: https://kb.pulsesecure.net/articles/Pulse_Secure_Article/KB12276
Dennis Hutten via observium wrote on 20.07.2020 10:49:
Small update. Pulse officially published a KB and recognized the bug.
https://kb.pulsesecure.net/articles/Pulse_Secure_Article/KB44533 https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fkb.pulsesecure.net%2Farticles%2FPulse_Secure_Article%2FKB44533&data=02%7C01%7Cdennis.hutten%40nxp.com%7C5167447383f04f4ea3be08d82c801d99%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C637308276057617369&sdata=Qz6a9TG5U4IVwWSMcGs6zQc%2B%2BtCGGcMsiNsq8rGWL9o%3D&reserved=0
My question for now is if we can manual manipulate the autodiscovery or a second identifier can be used for the autodiscovery? This way it will keep working with the pulse mibs.
Kind regards, Dennis
On 20 Jul 2020, at 09:29, Dennis Hutten via observium observium@observium.org wrote:
Caution: EXT Email
Hi Tom,
It is my first toughed too that the system description identifies it but if mike can confirm this it would be nice.
We will chase Pulse secure on getting the system description working again.
Dennis
On 18 Jul 2020, at 13:30, Tom Laermans via observium observium@observium.org wrote:
Caution: EXT Email
Hi Dennis,
We probably detect the PulseSecure part (it's not been Juniper for a while, right?) using the sysDescr. After your upgrade that is suddenly empty, which does seem like a bug?
The sysObjectId is .1.3.6.1.4.1.8072.3.2.10 which is not specific to Pulse but basically just says "This is Linux".
We should probably be able to detect if it's Pulse by polling another MIB variable - Mike probably has the best idea/solution for this :-)
Tom
On 7/18/2020 12:18 PM, Dennis Hutten via observium wrote:
Hi,
We upgraded a Junos Pulse VPN box to a newer version and since the device is changed to a Linux Device. Our service provider contacted also Junos but they couldn’t help they said in the first place.
Anything you can do to help getting the right discovery again?
Versions of Observium running in production – Stable, in LAB latest CE.
Example upgrade of a device changing from Juiperive to Linux in our LAB
2020-07-17 14:31:43 nlhtc-gclab-hpsa1 Vendor changed: 'Pulse Secure' -> ''
2020-07-17 14:31:43 nlhtc-gclab-hpsa1 Hardware changed: 'Secure,PSA-3000' -> 'Generic'
2020-07-17 14:31:43 nlhtc-gclab-hpsa1 Version changed: '9.1R6' -> ''
2020-07-17 14:30:02 nlhtc-gclab-hpsa1 Mempools: 1 deleted, 4 unchanged.
2020-07-17 14:30:02 Memory pool removed: mib PULSESECURE-PSG-MIB, index 0, descr Memory
2020-07-17 14:30:02 nlhtc-gclab-hpsa1 Processors: 1 deleted, 5 unchanged.
2020-07-17 14:30:02 Processor removed: type iveCpuUtil index 0 descr CPU Utilization
2020-07-17 14:30:02 nlhtc-gclab-hpsa1 OS changed: juniperive -> linux
2020-07-17 14:26:43 nlhtc-gclab-hpsa1 Hardware changed: 'PSA-3000' -> 'Secure,PSA-3000'
2020-07-17 14:26:43 nlhtc-gclab-hpsa1 Version changed: '9.1R1' -> '9.1R6'
2020-07-17 14:26:43 nlhtc-gclab-hpsa1 sysDescr -> ''
2020-07-17 14:26:43 nlhtc-gclab-hpsa1 sysObjectID -> '.1.3.6.1.4.1.8072.3.2.10'
2020-07-17 14:26:43 nlhtc-gclab-hpsa1 snmpEngineID changed: 80001F888095475A3E33B6405D -> 80001F8880C6DAC55E2309125F (probably the device was replaced). The device will be rediscovered.
2020-07-17 14:26:43 nlhtc-gclab-hpsa1 Device rebooted: after 18m 59s (Uptime: 18m 59s, previous: 1 year, 35 days, 1h 53m 35s, used: hrSystemUptime)
2020-07-17 14:26:43 nlhtc-gclab-hpsa1 Device status changed to Up
2020-07-17 14:11:31 nlhtc-gclab-hpsa1 Device status changed to Down (snmp -> ping)
LAB box, not Working
[root@nlhtc-gclab-mon observium]# snmpwalk -v3 -u Test -a SHA -A test0001 -l authNoPriv nlhtc-gclab-hpsa1.dtq.nl-htc01.nxp.com
SNMPv2-MIB::sysDescr.0 = STRING:
SNMPv2-MIB::sysObjectID.0 = OID: NET-SNMP-MIB::netSnmpAgentOIDs.10
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (49097) 0:08:10.97
SNMPv2-MIB::sysContact.0 = STRING: Eugene Lee
SNMPv2-MIB::sysName.0 = STRING: nlhtc-gclab-hpsa1
SNMPv2-MIB::sysLocation.0 = STRING: HTC038 TestLab
SNMPv2-MIB::sysServices.0 = INTEGER: 72
SNMPv2-MIB::sysORLastChange.0 = Timeticks: (0) 0:00:00.00
Production box, Working
[root@nlams01manp001v observium]# snmpwalk -c xx -v2c brcpqnwras001-int.br-cpq01.nxp.com
SNMPv2-MIB::sysDescr.0 = STRING: Pulse Secure, LLC,Pulse Connect Secure,PSA-5000,8.3R7.1 (build 65025)
SNMPv2-MIB::sysObjectID.0 = OID: SNMPv2-SMI::enterprises.12532.256.3.1
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (572322868) 66 days, 5:47:08.68
SNMPv2-MIB::sysContact.0 = STRING: Global Connectivity Team
SNMPv2-MIB::sysName.0 = STRING: brazil-ssl.nxp.com
SNMPv2-MIB::sysLocation.0 = STRING: Campinas, Brazil
SNMPv2-MIB::sysServices.0 = INTEGER: 72
SNMPv2-MIB::sysORLastChange.0 = Timeticks: (0) 0:00:00.00
Production box, not working – version 9.1R6
[root@nlams01manp001v observium]# snmpwalk -c xx -v2c demucnwras001-mgt.de-muc01.nxp.com
SNMPv2-MIB::sysDescr.0 = STRING:
SNMPv2-MIB::sysObjectID.0 = OID: NET-SNMP-MIB::netSnmpAgentOIDs.10
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (312846981) 36 days, 5:01:09.81
SNMPv2-MIB::sysContact.0 = STRING: Global_Connectivity@nxp.com
SNMPv2-MIB::sysName.0 = STRING: demucnwras001-mgt
SNMPv2-MIB::sysLocation.0 = STRING: Munich, Germany
SNMPv2-MIB::sysServices.0 = INTEGER: 72
SNMPv2-MIB::sysORLastChange.0 = Timeticks: (1) 0:00:00.01
Kind regards,
Dennis
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fpostman.mem...
observium mailing list observium@observium.org https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fpostman.mem...
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
participants (3)
-
Dennis Hutten -
Mike Stupalov -
Tom Laermans