The most recent content from our members.
Hello, I have approximately 300 Cisco devices that don't have the hardware health sensor option enabled. Since creating a resource list for all of these devices would take hours, I want to enable the hardware health sensor option in bulk from the database. How can I do this?
Has anyone faced issues with monitoring the hardware health of Huawei and Fortinet devices through SolarWinds? If not, could you please share the action plan or steps you followed to ensure successful monitoring?
The following are Hardware Health (Node) variables which can be used with alerts. Overall Hardware Status (Node): ${N=SwisEntity;M=HardwareInfo.CategoriesWithProblems} ${N=SwisEntity;M=HardwareInfo.CategoriesWithStatus} ${N=SwisEntity;M=HardwareInfo.DetailsUrl} ${N=SwisEntity;M=HardwareInfo.FullyQualifiedName}…
This produces no results. MIB and Row ID are correct. Numberic Value should produce a hit. Anyone see anything wrong with my logic? SWQL SELECT E0.[Uri], E0.[DisplayName] FROM Orion.NPM.CustomPollerAssignmentOnNode AS E0 WHERE ( ( ( E0.[CustomPoller].[UniqueName] = 'tempSensorValueInt' ) AND (…
I have a device displaying this message "Alert me when any hardware component goes into a warning or critical state". The error is on a port that is administratively shut. I checked the alert on solarwinds and the trigger is set to when the hardware sensor is equal to warning and another when its equal to critical. But the…
Currently Hardware sensors are only related to the Node, which is fine for some things like temperature and such. However, for sensors that are directly related to an Interface, such as monitoring SFP's that support DOM for things like Tx/Rx power, temp, bias and such it needs to be associated with the interface and not…
Hi, Please let me know how to reach out support manager as my SAM module related case pending since last 30 days but not getting proper support and reply. Thanks.
This feature request pertains to the support ticket #00031386 The hardware sensors gather information such as current usage (mA), TX and RX levels (dBm) etc. Whether an interface is "shutdown", "notconnected" or "connected" in the device, the web interface shows values for the sensors belonging to the interfaces. In the…
Currently in NPM, the selection of interface monitoring and the hardware sensors for those interfaces are completely independent of each other. When adding a device, and NOT choosing certain interfaces, you still end up with hardware health data on those interfaces (usually which is moot). Furthermore, even if the…
Do not display hardware alerts (red) for sfp (small form factor ports) ports that are administratively down. Reference Thwack Article: https://thwack.solarwinds.com/t5/Alert-Lab-Discussions/Problem-with-hardware-sensor-alert/m-p/236150 Reference Original SolarWinds Case#: 00539759 - Possible false/positive when monitoring…
It looks like you're new here. Sign in or register to get started.