batusek

Hi njoylif, there were no major improvements of the hardware health monitoring in NPM 10.7. However, we might consider some improvements in the further release. Would you be willing to cooperate and giving some some initial feedback to the early implementations?

Bryan, please open the ticket anyway - either support or sales engineering should try to help you.

Could you please open a support tickets and attach there: - diagnostics - SNMP walks from the device - contents of the NPM_RoutingTable Then please paste the ticket number here. Thank you.

Hi telmuun1211, have you tried NPM 10.4.1. This should fix the problems with bias sensors. If there are still some problems remaining after the upgrade to 10.4.1, please contact us again. Hardware health monitoring is still quite a new function in NPM and we are constantly working on improvements and further tuning it on…

Hi charliedontsurf, unfortunately, there is no such command. You would have to do it directly in the database. If this issue is urgent for you, please open the support case and post its number here. You can also disable the alert causing you trouble (I mean just the alert - the hardware status monitoring would keep…

For per node setting, you can use the table NodeSettings. Just add one row for every node with SettingName=NPM.RoutingTablePollInterval. Again, this is in minutes.

Hi ser, I guess you have already been using NPM 10.4.1. We would be interested in your experience with this version. Do you think it would be possible to send us MIB walks of devices with bias sensor still reporting an alarm? We are constantly working on improvements of hardware health monitoring and your feedback is…

Bryan, could you be a little bit more specific? Which version of NPM/NCM do you use? When this error occurs? Is there anything in the Orion log files? Anyway I think opening a troubleshooting ticket to NPM support is probably the best approach in this case.

Doesn't you SQL server have multiple IP addresses? Isn't one of them equal to your next hop router address? Also - is this a NPM problem or does it show the same next hop address also on the device?

Hello, there can be multiple reasons. For example, multicast routing is currently supported on Cisco Devices only. If your devices are from Cisco, you can try to check the following: * ipMRouteEnable (1.3.6.1.2.1.83.1.1.1), returns '1' * ipMRouteEntryCount (1.3.6.1.2.1.83.1.1.7), return value must be higher than 0 Robert

You might want to try several recipes mentioned in http://thwack.solarwinds.com/message/187550#187550

Hi epenney, NPM currently doesn't support hardware health monitoring on H3C nor 3com devices. If you wish them supported, you can raise a new feature request.

Hi charliedontsurf, have you tried ideas recommended in this thread? Especially using CISCO-ENVMON-MIB could help you. Robert

Extreme AP are currently not support. You could raise a feature request and product management might consider it for future releases.

Routing table poll interval is driven by the setting NPM_Settings_Routing_RouteTable_PollInterval in the Settings table, by default it is set to 180 minutes. You are right, it uses SNMP. Be careful however - as routing tables are big setting too short poll interval creates a certain load to the polled device and the device…

Hello artb, from your question it is not clear to me, which NPM feature do you use. Is it Hardware health monitoring or you try to define a custom poller? In principle, HWH pollers read only status of the devices - you have to set the threshold on the device Custom pollers currently do not support thresholds.

Hmm, looks suspicious. Could you please open a support ticket and submit there an SNMP walk of this device? Then post the ticket number to this thread.

Hi strebzilla, it would help us, when you write, which Cisco devices you use. Also, which sensors have been detected by NPM (fans, temperature, etc.). Robert

Robert, thank you for your feedback and I am sorry for my late answer. What you describe was an inital behavior of NPM RC1-3 and has been reported several times by customers (see e.g. Re: NPM 10.4 RC1 Hardware health on Juniper Switches - Virtual Chassis or Re: Hardware Monitoring Issues with Juniper Devices). Based on the…