zizi

NPM is able to populate list of IP addresses using DNS server and SNMP or WMI. IP address poll for SNMP node executes these steps: * Perform reverse DNS lookup on Node's IPAddress (from Nodes table) to get fresh DNS name * Perform forward DNS lookup on DNS name from step 1 * Query ipAdEntIfIndex OID (1.3.6.1.2.1.4.20.1.2)…

I'm sorry, I've tested this on my developement machine and it worked. It is possible that my environment didn't match yours. If my DNS records were set-up correctly Orion worked. Dynamic IP address was updated correctly during rediscovery.

Hello, Orion NPM 10.2 is no longer using discovery engine for collecting topology data. It utilizes new topology pollers instead and polls topology during node rediscovery. Upcoming Orion NPM 10.3 is now able to utilize LLDP/CDP information. You can try signing up to BETA or RC program to give it a try before 10.3…

Unchecking L3 pollers forces Orion to stop polling ARP table data, which means it won't collect and utilize them for creating connections. The only affected feature is topology, so it should be safe to disable L3 polling. Connections based on ARP tables are not reliable, so it is most likely issue with Orion reading the…

Orion NPM 10.2 tries to perform reverse DNS query only for static Nodes (is Dynamic = false). It executes it as part of each Node status poll. All nodes which discover via SNMP get their Caption by polling sysName OID using SNMP. Once Orion sets up Caption for the first time, it never touches it again, until user manually…

Layer 3 topology poller is responsible for collecting ARP tables from SNMP enabled devices. Data from ARP table are used in topology calculation. Sometimes the calculation provides better results without using ARP data, or ARP tables are so big, that it causes polling performance issues. In such cases it is better to avoid…

Orion NPM is polling sysUptime OID for you automatically out-of-the-box. It also automatically computes Last Boot value from current sysUptime counter value and is able to alert based on that value. Orion stores both current sysUptime counter value and computed Last Boot in database, please notice SystemUpTime column…

One packet sensor is able to monitor one network interface only. You should be able to configure you network gear to deliver all traffic to one mirror/span and connect it directly to NIC monitored by network PAS, though. Network sensor deployment is designed in a way, that one sensor should be responsible for monitoring…

ConnectNow feature is still collecting all the data mentioned in post linked above, but it has been improved over the time, so it now supports also CDP, LLDP, STP for L2 and IP forwarding data collection for L3.

We have reworked Orion's H3C poller implementation in upcoming NPM 10.4. It would be great if you can provide some feedback related to new CPU & Memory polling in 10.4.

You can actually see the lists of OIDs used by NPM in the snmpwalk.exe. Please notice that snmpwalk.exe lists all OIDs supported by device. It basically asks for all of them. This operation is also known as a MIB walk. Tool is not performing any filtering to display only OIDs, which Orion is able to utilize, it simply…

We've seen some issues with Message Queuing (MSMQ) in the past. Many Orion services are depending on MSMQ, which mean they need to be able to communicate with MSMQ service to work properly. As Orion Module Engine was unable to use MSMQ, it wasn't fully initialized and most likely just got stuck in a start-up phase. That's…

You should not install NPM 10.1.3 on Windows 2012 and SQL Server 2012, as such configuration is not officially supported. According to release notes, support for SQL 2012 was introduced in NPM 10.3.1. Windows Server 2012 is supported in NPM 10.4 and later versions.

Orion utilizes sysObjectID OID 1.3.6.1.2.1.1.2 and matches its value against built-in database of known SysObjectIDs to get vendor name and machine type, which is then displayed on Node Details page. Your device is returning "0.1", which does not seem to be a valid value for DELL. As Orion is collecting sysObjectID…

If you uncheck L3 topology poller on a Node, Orion stops collecting ARP table data for it. Orion is able to utilize ARP table data for building topology connections, in case there were no other connections made just using Bridge table, LLDP or CDP (L2 topology poller). The worst case scenario is that some most likely…

Can you check Orion Events table for multiple "Removed" or "Added" messages about Nodes, Interfaces and Volumes occurring at the same time? Also check Debug.log for database connectivity issues. I remember a case, where all nodes were removed and re-added every morning, because of broken database connectivity.

You can use Background Inventory, which Orion ordinarily uses during upgrade from previous versions to automatically assign new pollers for CPU, Memory and Topology. Background Inventory needs to be configured manually in Orion Database. You can use SQL statement below to enable re-inventorying of L2 and L3 pollers for all…

NPM is performing DNS name or IP look-ups to keep IP and DNS fields in sync. Reverse look-up is performed for all static nodes during regular node status poll. Forward look-up is performed for all dynamic nodes during regular node status poll. Depending on your Windows configuration, the look-up might be performed using…

Orion NPM polling requires read access to you device over SNMP. You don't need to configure traps, unless you want Orion to collect them. To configure SNMPv3 polling on a Cisco device, you may want to: * Define an user group, create and assign a view to the group * Define an user account, assign account to the group *…

Are you able to open a support case and provide a SNMP walk from the device? Please use built-in snmpwalk.exe tool from Orion install directory. Please post back with a case number here, so I can take a look.

Orion NPM 10.2 is no longer using discovery engine for collecting topology data, it uses new topology pollers instead. Topology pollers are assigned to all devices automatically during upgrade to 10.2 and are also visible in List Resources tree (device support needed). Orion now polls topology data during regular node…

Can you please use list resources on both your HP switches and make sure there are L2 topology pollers available and selected on at least one of them? Connections created using ARP table data are less accurate than Bridge-MIB or Q-Bridge-MIB connections. If at least one of those two HPs has L2 poller assigned, please open…

Orion status poll is sending out one ICMP Echo Request packet out. If ICMP Echo Reply is received within defined timeout (2.5s by default), it means that Node is responding and Orion marks its status as UP. If no reply is received, Orion applies retries policy and tries sending ICMP Echo Request again. Default number of…

Can you also post your snmp-server host here? That's the one responsible for traps configuration.

Orion is composing Node Caption using this algorithm: * If sysName is known, use it for Caption * If DNS name is known and sysName is not, use DNS * If both sysName and DNS are unknown, use IP address There is no configuration option available which could change this default behavior, but once Caption is set, you can edit…

NPM polls for IP addresses as part of Node Rediscovery process. So content in NodeIPAddresses table should be updated every 30 minutes, by default (rediscovery interval for nodes). You can also force update by clicking on "Rediscover" on Node Details page or for multiple nodes in Web Node Management (More Actions ->…

This issue occurs when NetPerfMon service is unable to refresh elements from Orion Database. Service keeps its own internal representation of all Orion elements (Nodes, Interfaces..) in memory and tries to sync it with Orion Database every 30 s. I've seen cases when SQL query used for refreshing elements returns zero rows…

Orion is unable to collect L2 topology data for Windows boxes. I've found this article, which describes supported management information base on Windows: Management information base support in Windows 2000, Windows XP, Windows Server 2003, and Windows Vista Orion is able to utilize Bridge, Q-Bridge MIBs for getting L2…

You should be able to use Mode Management for this task. Just locate your node in the list, expand its child entities by clicking on "+", select old Volume and hit Delete button. You can then use List Resources to add new volume, if needed. Marek Zizlavsky SolarWinds Developer

Do you also see a matching Interface Removed events? Which version of Orion NPM are you using? Following information is relevant for Orion NPM 10.1 (and older): I remember cases where removed/added events were generated for all elements when NetPerfMon service (Standard Poller) was unable to refresh data from Orion…