zizi

Orion started polling all IP addresses assigned to managed nodes. Addresses are stored in NodeIPAddresses table in Orion database. This is a new feature of Orion NPM 10.2. Orion is able to utilize DNS and SNMP or WMI to get this information. For all SNMP Nodes: Orion polls ipAdEntAddr (1.3.6.1.2.1.4.20.1.1) OID to get list…

Ok, no need to create a support case. I've notified product management already. Thanks for the feedback.

Polling of L2 and L3 topology data might be disabled by removing topology poller assignments from Pollers table in Orion Database. To remove all L2 and L3 topology pollers, please execute this SQL statement: DELETE FROM Pollers WHERE PollerType LIKE 'N.Topology.SNMP.%' To remove all L2 topology pollers only, please execute…

Forward DNS query is performed with each status poll for all dynamic Nodes, as Orion has to make sure it uses a valid IP address before it sends out the ICMP echo request. Default Node status poll interval is 2 minutes.

You can use this query to check, if Orion keeps record of more then two CPU cores for the node in the past: SELECT * FROM CPUMultiLoad WHERE NodeID = 123 AND CPUIndex > 1 Don't forget to replace 123 with the correct NodeID again. If the query returns some rows, you should be able to see the time frame when machine was…

Can you please post back with the feature request ticket number here? I would like to add some info there. Thanks!

Can you please provide more details about the web.config? Where was the file located? Is it the web.config file of Orion Website or a web.config of another site hosted on a box where sensor was deployed? If it was Orion Website's web.config, I can imagine that upgrading to newer version of NPM simply overwrites existing…

Haven't you unassigned 2 cores from your VM recently? That will explain the issue. I've found out that if I manually insert new row for 3rd CPU core for machine, which has two CPU cores physically, into CPUMultiLoad_Detail table, Orion starts reporting 3 cores for such node. So if your machine had 4 CPU cores in the past,…

Yes, Poller Checker Tool is also an option. Please be aware, that the tool was designed for advanced users, so it is not performing any "smart" checks to prevent you from messing up your Pollers table. List Resources is much safer option ;-)

Orion uses SNMP protocol for collecting topology data, no other management protocol is supported. There are various MIBs and tables, which contain topology related information. Orion NPM 10.2 was able to collect information from Bridge Table (forwarding info) and ARP table (a.k.a. L3 data). Thanks to topology improvements…

Are you able to open a support ticket and upload diagnostics + a screenshot of the map with incorrect & missing connections highlighted? Please post back with the case number. Thanks.

Layer 3 topology poller is collecting ARP table data, which Orion may use for building topology connections. ARP table may help to add some missing connections between nodes, but sometimes it just adds a false ones. Information from ARP table is not very reliable, because it contains both direct and indirect connections.

This behavior might be considered as a known UI defect in List Resources dialog. It should not offer CPU & Memory polling check-box. We already have this issue filled in in out internal bug tracking system.

Thanks for the quick reply. It is expected that NPM data should match list provided by SNMP agent. You can try to review IP address binding settings on the device itself and compare the list to the output from SNMP agent. As Orion relies on provided SNMP data, I'm afraid there is not much we can do, if those are corrupted.…

Polling Rate engine metric was introduced in Orion NPM 10.2, there was no such metric in NPM 10.1.3. Orion 10.1.3 was counting SNMP queries used for collecting statistics (interfaces counters, CPU & Memory) and exposing this number as "SNMP statistics Polls per second". 10.2 is using completely different metrics for…

Hello Ciaran, Are you able to collect MIB walk from your device using built in SnmpWalk.exe tool (located in Orion installation directory)? Also, please provide a screenshot/information from device's console, so we know which are the valid values for memory size and memory used reported by device's OS. Thanks, Marek

I've seen devices which respond to both 32 bit and 64 bit variants of OIDs, but provide incorrect values for 64 bit ones.

You can also exclude the "AND NetObjectID IN (1,2,3,4)" part to remove topology pollers on all Nodes in your DB.

You can create "Current Status of Nodes, Volumes, etc" report in Report Writer and add Network Node -> Node Details -> Last Boot field. This report will provide you Date and Time when node was rebooted for the last time, computed using system uptime counter value exposed through sysUptime OID. If you need to display real…

You can find list of all "topology related" OIDs polled by Orion in SolarWinds Knowledge Base :: What object IDs (OIDs) does the Orion Platform poll for network topology information? KB article. When List Resources dialog doesn't list L2 or L3 check-boxes, it is possible that the device still supports required MIBs, but it…

Would it be possible for you to open a support ticket? I need full Orion Diagnostics for further troubleshooting. Please post back with a ticket number here, so I can take a look. Thanks!

Value displayed on gauge is stored in Nodes table in CPULoad column. Values for multiple CPU cores are stored in CPUMultiLoad_Detail table, including historical data. To find out if there was any issue with storing those values, we would need to see output of SQL query "SELECT * FROM CPUMultiLoad_Detail WHERE NodeID =…

The KB article, you've mentioned is describing how to disable topology calculation. Calculation takes raw topology data from Orion database and computes connections between devices. Those connections are then stored into TopologyData table. KB procedure is not disabling topology polling, just the calculation. Right now…

Are you managing both end-point interfaces of those CDP connections in Orion? Have you noticed any connections with unknown source or destination interfaces on NPM Topology resource for the main switch ("?" instead of interface names)?

Thank you for the diagnostics. It seems that "sofaware technologies" devices do not support any OIDs, which Orion is able to utilize for polling memory. Orion found a suitable poller for CPU, because device seems to be supporting NetSNMP agent OIDs. Unfortunately, Orion needs both CPU & Memory OIDs to poll the device…

Orion uses one set of SNMP credentials for polling and for traps receiving. It means you need to add your device as SNMP node to Orion and use the same community string for configuring traps. Basically it should be enough to specify Orion polling engine IP address as trap destination in device configuration and configure…

Orion supports community string indexing, which is a technique used by Cisco for exposing bridge table information for multiple VLANs over SNMP. Orion has two variants of bridge table pollers, for example: * N.Topology_Layer2.SNMP.Dot1qTpFdb - variant which utilizes community string indexing and collects info for all VLANs…

Orion is not able to collect topology data for ICMP nodes, because ICMP protocol itself is unable to provide such information. It means that ICMP node itself is not able to provide any relevant topology information to the system. Orion is currently able to collect topology information for SNMP nodes only. ICMP node does…

Orion is cleaning topology data tables during regular database maintenance. It deletes topology data related to nodes which were deleted, or nodes which no longer have topology pollers assigned. So it takes some time, but the incorrect link should get removed at some point. If you eventually decide to open a support ticket…

Hmm, that should be correct. Are you able to collect a WireShark capture containing a couple of incoming traps from affected device and open a support ticket?