zizi

Orion NPM 10.2 changed default behavior and reverse DNS look-up is now no longer performed for all dynamic Nodes, regardless of current "disable reverse DNS" setting. Setting now applies to non-dynamic Nodes only. Work-around mentioned in this thread is no longer necessary (valid), as it is working correctly out-of-the box…

I've made some investigation about this problem. Orion NPM correctly handles IP address changes of monitored devices when valid forward DNS record with updated IP is present in DNS. Missing or mis-configured reverse DNS record seem not to be a problem for NPM. Monitored device IP address is automatically updated during…

Orion is able to compose Node Caption based on SysName for SNMP and WMI nodes. If it's impossible to poll and use sysname, it uses reverse DNS look-up on Node's IP address to get FQDN. If also reverse look-up fails, Orion falls back to using Node's IP address. Both Discovery and Add Node Wizard use the same logic for…

Orion NPM 10.2 is able to utilize information from bridge forwarding and filtering tables (Bridge-MIB and Q-Bridge-MIB) and ARP tables (ipNetToMedia table in IP-MIB). Incorrect connections are often built using ARP table data. Orion utilizes ARP table only if no other connections were discovered using bridge forwarding and…

Can you please specify which version of Orion NPM product are you using?

We've seen cases when device reported up to 300.000 records in ARP table, for instance. In such cases it might really cause network performance or traffic issues, as amount of information, which needs to be polled, is quite huge. That was the reason why we introduced a separate Topology Poll Interval in 10.3 and also…

Orion uses ICMP for node status and packet loss monitoring. Are you able to "ping" to those nodes from machine, which hosts Orion polling engine? As SNMP is not used for status or packet loss monitoring, any issue related to SNMP should not be relevant.

Hello, Unfortunately, it is not possible to change it right now. Currently there is no way how to change fast poll frequency, because 10s interval is built in into the product and it is not user configurable. You can open a customer feature request for implementing this kind of functionality in Orion, if you find it useful.

Orion NPM 10.4 added a new resource Node Detail Reports -> All IP Addresses on ${Caption}, which displays all known IP addresses assigned to a node. It might be assigned to a Node Details View. Resource is able to highlight the IP, which is used for polling. You need to use Edit Node page to change the IP used for polling.…

Orion NPM is able to poll CAM tables from devices using SNMP. Information is stored in NodeL2Connections table in Orion Database. Orion uses this information for topology calculation. Table should be also exposed via SWIS, so you should be able to use Custom Query Resource to display the data. Available pollers for getting…

This setting applies to both L2 and L3 topology pollers. It is stored on per node basis in NodeSettings table. Setting name is "Core.TopologyPollInterval". You just need to create a new row with matching NodeID, SettingName and Value (in minutes). There is also a Orion-wide setting available in Settings table with…

Orion Website won't allow you to delete a system view, so you may need access to your Orion Database and remove this restriction manually. You can use SELECT * FROM Views query to list all your views. Once you identify a view (row), which should be removed execute UPDATE Views SET System = 'N' WHERE ViewID = <ID>, just…

List resources needs to discover which OIDs are supported by the device and assign appropriate pollers for CPU, Memory, topology, etc. This operation may take some time. Orion is not showing any progress for poller discovery part, like it is showing for interfaces and volumes. It may be enough just to wait a little bit…