Comments
-
Lets try to get the NTA migration tool we really need - thanks for your support:
-
Does anybody know if the Default Config Purge Job is scheduled and active as default?
-
Correct - XY coordinates worked for us too (Microsoft Dynamics Frontend check with WPM) :-)
-
Running NCM 7.2.1 on the same server with no errors.
-
Any news about the official release of the SCOM 2012 connector?
-
Try polling the Nexus boxes with SNMP v1 - I have seen this work before :-) It seems like the Getbulk function in v2 could stress up the Nexus nodes in certain scenarios
-
Any news here? Would be REALLY great if the report could recognize minor releases and eliminate some of the false positives!
-
OK - I solved the problem by changing to SNMPv1 on the Nexus nodes. Explanation: One of the changes in the new versions of NPM is that NPM use SNMP GETBULK requests when polling a node. Some devices do not like it and will fail to respond. To correct this, set the device to SNMP v1 and NPM will poll using SNMP GET requests…
-
jacob.decker Thanks! That worked perfectly :-)
-
Hi, My input here: Get the extra server for NTA flow storage - the improvements in performance is HUGE compared to placing this on another server shared with other stuff. The time and money spend on spinning up an extra VM for this is VERY well spend on the long run :-)
-
You can use the "POP3 User Experience Monitor" or "IMAP User Experience Monitor" in SAM.
-
Remember to run the Solarwinds.SEUM.AgentDomainConfigurationTool.exe and set up the 2 users executing the playback recorded. The 2 users have to be domainusers and have access to the portal You are testing.
-
Add a SAM template with a HTTP monitor to the server that has access to the Remote web service. In the settings of the HTTP monitor You specify the URL of the SOAP web service. Done.
-
Now - I dont know which nodes You are trying to poll in real time with Solarwinds... But if You "realtime poll" on all nodes, You could end up stressing eg. some types of switches and that would end up in a SNMP downprioritizing on these nodes. (If they have more relevant things to do, the SNMP will simply be…
-
APE on a new server (Virtual or Physical). But check the All settings, polling engines page first - if the polling completion value is 100 at all times and the polling rate is not reaching max, then you dont necessarily need a new APE yet.
-
-
Did anyone solve this? I am seeing some flapping interfaces on our Nexus 5548 & 5596UP nodes too. It seems like these boxes are stressed by the SNMP monitoring somehow.... NPM10.4.1 and running SNMPv2C against the Nexus nodes.
-
Try this in Message Body: Root Cause: ${N=OrionGroup;M=GroupStatusRootCause} Group has currently been down for ${N=Alerting;M=DownTime} Minutes Link to Group: ${N=SwisEntity;M=DetailsUrl} Acknowledge: ${N=Alerting;M=AcknowledgeLink}
-
https://thwack.solarwinds.com/docs/DOC-170557#start=25
-
Here You have a link to a goldmine of Compliance Reports, made by COURTESYIT : Cisco STIGs
-
We would like to use the API to integrate IPAM with Service Now......
-
I am also seeing a Hardware Health Warning on a Cisco 3560: Te1/2 Receive Power Sensor, Major Warning. The interface is shut down. Running NPM 10.4.1. After upgrading to 10.4.1. a lot of ghost alarms disappered, but we still have a few left. It could be great if NPM ignored these alarms if the interface is status: shutdown.