jbiggley ✭✭✭✭✭

Yeah, don't forget that the Configuration Wizard has to be run after each module install. You can't stack them. Yes, it means that if you are doing a 4 or 5 module fresh install that you have to run the configuration wizard 4 of 5 times. If NPM is in the mix, install it first. If SAM and no NPM, install SAM first. Hope it…

Is this a fresh install or an upgrade? If fresh, then try uninstalling and re-installing SRM. It sounds like an SQL update statement isn't working. Support should be able to help you with that fix pretty quickly if it is code related.

I can confirm that Balki 1429 said. There is a query you perform against the DB and it removes the federated collector. Engage support and you should have it taken care of with 24 hours.

Here are the queries that I am planning to use to clean up our discovered interfaces and volumes as per the rules that we have established for our environment. These might get a little more complex as I'm considering excluding network devices from this list as they are handled just a little differently from our other…

Did I miss something? When I built my scheduled discoveries I did so from a single polling engine. While testing today I got this error. Do I need to assign discoveries based on the polling engine to which the node is currently assigned? bluefunelemental‌ jeremy118‌ Node REDACTED, Import Status: skipped, already monitored…

I wish it was that straight forward, but it isn't the Type of Property. I've checked the advanced alerts and there haven't been any changes.

Quick update -- this is only an issue in Firefox, not IE.

Just sent an email to the guy who was voluntold he was replacing me at my last company. Hopefully Graeme reaches out to you!

The SQL query would like something like this: SELECT Nodes.MachineType AS Machine_Type, Nodes.MachineType AS Machine_Type_1, Nodes.Caption AS NodeName, Nodes.IP_Address AS IP_Address, Nodes.IOSVersion AS IOS_Version, Nodes.IOSImage AS IOS_Image FROM Nodes ORDER BY 1 ASC You have two options. You can either directly query…

*bump*

As I understand it there are two points of data collection, each presenting data in a separate layer of the Orion UI. It sounds like you own NPM and VMAN. NPM still relies on SNMP to collect detailed data from a node. VMAN collects detailed statistical data from the same node via the vCenter API or, if you don't have VMAN,…

sja​ from what I understand from support Rabbit MQ is replacing *most* of the functionality of MSMQ but MSMQ is not being replaced entirely. Perhaps cobrien​ can clarify for us.

I guess the magic ingredient is patience. When I checked this morning all of the values are there. Obviously there is some process that runs that updates the UI and doesn't update right away. I still think this should be escalated to engineering for testing and validation stevenwhunt‌ but for njoylif‌ and the rest of us --…

I've opened case #857622 to track this issue. Fortunately this is in our POC environment. Unfortunately, I plan to upgrade our entire environment to NPM 11.5.x, SAM 6.2.x and NTA 4.1.x in September. If this doesn't get resolved I am going to be a big trouble as it is something we do extensively with Orion 2014.2.1 today.

Yeah, we dealt with a lot of that same sort of regulatory compliance stuff, especially as we push into the international space. A polling engine in the management plane is the way to go. Agents are a fantastic way to get around the firewall issues (although not completely as they still need to be able to talk to/from the…

Just as an update, I wonder if I have to enable the **Directory analysis enabled flag (which defaults to false) under the advanced analysis options? I'm going to try it and I'll post back to let you know. Cheers.

Network Automation Tool | Solarwinds This link says "10K elements per poller" I have 17 polling engines. Does that mean I can have up to 170K elements on a single instance? What is the maximum number of pollers per primary server now? So many questions!

Now, I don't actually know the answer for sure. (It's true -- MVPs aren't unending sources of knowledge! Opinions, yes, knowledge, no. ) That said, if you look in your database you'll find a table called AlertConditionState. AlertConditionState has a column called AlertID. That AlertID links that triggered instance of an…

I've been thinking about this one a little more and I've got a few comments to add. 1) The issue with adding them to the database is the size of the environment. If I am adding hundreds of nodes at once I risk impacting the performance of the Orion server with elements that I am not going to monitor. When you are hosting…

OK, I think we've stumbled onto something very interesting. As a recap, we do our URL monitoring by assigning a SAM template with HTTP response monitors to an external node (specifically a DNS server from one of our ISPs). Doing so lets us measure response times from an external point back to our internal network. After…

Dang -- that doesn't work. I queried the NodesData table and the community string for SNMP is already there! The 'work around' means that the SNMP string is populated even through you change the node polling method. This worked for SNMP to WMI but doesn't appear to work for SNMP to Agent. DOH!

Update: I tried configuring a node with SNMP after installing the agent and even though I configured the agent to 'Include SNMP Credentials' I have been unable to assign custom pollers. I don't want to have to use the workaround but I am getting desperate at this point....

So after some testing (and a recommendation from zackm​) the answer to this question is YES -- the Windows agent does support a TCP component monitor, but you have to make a small change to the application monitor. When you build an application monitor, the preferred polling method is 'Agent'. That is what forces the TCP…

OK -- testing done. Here's the outcome -- if you disconnect an interface you will get an event for both the interface and monitored node going down -- there are no implicit dependencies built into NPM. For us, that means that the triage process is going to have to be rock solid so that we don't create incidents for nodes…

A component is an individual part of an application monitor. An application monitor is an application template applied to a node. Each template (and monitor) is made up of individual components that monitor different aspects of an application and/or server. In this case, the default alert will notify you if any particular…

Oh, one more --- one more. "I didn't back up any of my data. Is there any way to recover it?" Err, no.

"Why did it break?" That was the question I hated end-users asking. It's one thing if it is a enterprise environment and something goes wrong. Enterprise applications and infrastructure are tightly (ahem!) controlled eco-systems. Why did that desktop application crash just now? I have no idea. I can fix it for you, or I…

I just wanted to point all pre-NPM12 customers to this great post by xtraspecialj​ Re: Orion Alert History Table Retention (Post NPM 11.5)​ We found found that the C:\ProgramData\Solarwinds\Logs\Orion\Alerting.Service.V2.log had a ton of LONG RUNNING QUERY entries...like more than 7000 in the last 24 hours! When we dug…

As promised, here is my 'post-reboot update'. No change. The SWISv3 process still hovers around the 28-30% total CPU utilization on our 8 CPU server. It *did* switch to CPU 4, but that CPU is still running hot.

Quick Monday morning update. Our primary poller in our production environment is still displaying the same CPU usage profile, however is occurred to me on the weekend (What? You don't think about monitoring problems on the weekend too??) that I should check out our dev environment. Granted, dev is currently a single poller…