Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Pulse Secure Appliances Show as Different Machine Types

I have two PSA-3000's that I have added to Orion and when they were added one shows the machine type as net-snmp - Linux and the other one shows as Neoteris, Inc. The one that shows as Neoteris I am able to pull the correct CPU and interface information, the one that shows as net-snmp I am not able to pull the CPU or interface information. Does anyone know how to change the machine type so that I can pull the correct information?

Find more posts tagged with

Accepted answers

All comments

cnorborg

Huh, thought this would be an easy answer, you used to be able to set it in "Node Properties" where there was a dropdown of node types, and it was usually just set to "Auto Detect" or something like that.

Investigating further, but anyone else know where it went? Or am I just missing it?

cnorborg

You know, before I tell you a potential way to solve it, should probably try the easy ways first. I know when I added our 4 Pulse Secure 7000-f's, one of the 4 got added a little oddly where instead of seeing it as a box with 8 CPU's, it thought it only had 1. The first thing to try is to do a "Rediscover" followed by 3 or more polls after it, maybe a couple times. If this doesn't change anything. Try deleting the node completely and re-adding it. That worked for me. I think the CPU on the node was too high to let SNMP do its thing fully when I initially discovered it. Not 100% sure.

If that doesn't work, you can edit the "NodesData" table itself using the Database Manager on the server. I'm guessing you might have to change the "Vendor" and the "MachineType" to match the one that was discovered ok. To limit the data seen to only the nodes you want to work with, use a query like this:

SELECT TOP 1000 * FROM [dbo].[NodesData]
WHERE (IP_Address IN ('10.1.1.25', '10.1.1.82'))

When it brings up your two nodes, click on "Enabled Table Editing" and change the values in the two fields I mentioned so they both match the "good" node. This is kind of a last resort though, but I think it should work. Then rediscover and poll... If it doesn't work, delete the node and re-add it again.

dchristensen

Sorry for the delay in responding, I appreciate your suggestions. After doing what was suggested the still displays incorrectly. I beleive that it is due to the sysobjectid of 1.3.6.1.4.1.8072.3.2.10 that Solarwinds is somehow using to identify the tyoe of node. The one that does display correctly has a sysobjectid of 1.3.6.1.4.1.12532.256.2.1. In addition to the items you had suggested to update in the DB I had also modified the sysobjectid in the DB to be the (what I assume) to be the correct one with the same result. At this point I believe I will open a ticket with support to see what they may suggest. Again thanks for you suggestions.

ashley.heilbronn

@dchristensengive this customer poller I created a try, I wasn't happy with what solarwinds native poller was doing in how it it was processing snmp data.

When you import the poller and assign it, your pulse nodes will display this.

Pulse Secure Node Details.zip