FormerMember ✭✭✭

I like it. Neat idea, thanks! On Dec 9, 2012 7:12 PM, "Steven Klassen" <

Hi, If you go into the NCM Settings (From the Config Summary screen) on the right hand side there's a link called Global Device Defaults. From here you can set the default switch username and password and also the connectivity method. Regards Jason

Well, that's another good approach I'm not sure why the Interactive bits weren't working right, but this works. Are you on 5.5 or 5.6?

I have this same issue and no solution yet besides manually removing the volumes from the database. I use this custom SQL report to track those volumes with a non-unique drive letter: SELECT dbo.Nodes.Caption, dbo.Nodes.IP_Address, LEFT(dbo.Volumes.Caption, 3) AS Expr1, COUNT(*) AS Expr2 FROM dbo.Volumes LEFT OUTER JOIN…

i second this request....

saw this in another thread about a firewall issue were you trying to push this through a firewall? if so you might be able to change your firewall filter to allow the extra data if you wated to.

AMSW, It's a feature request. It's something we want to do, but we don't have a date.

 In 9.1, we did some work to look for interfaces that belonged to nodes that were longer in the database. When we found one, we marked that interface deleted. DB Maintenance cleans out all the data from the database associated with those orphaned interfaces. Now, I'm amazed that it took as long as it did, but I'm guessing…

Good Morning Alterego! Yepp, I can confirm the SQL Server instance is exact the same as in the SQL configuration defined and it does not make difference if it is a named instance or pipes. The problem was that the sql browser usually handles multiple instances - depending on the option for the port (default/static). In the…

I too upgraded Orion to 9.5 SP1. Two pollers, both are now stopped and will not restart. Ticket opened w/support and diags uploaded. My 9.5 upgrade is not going smoothly. Web is very slow and various other functions not working properly.

We have a fix that we will roll into an upcoming service pack; however, if you contact Support, you can get a fix just for the memory leak.

What version are you using?

 How do I get the RC? I'm still evaluating SW. thanks Dave

Have you added any Layer 3 devices to UDT? That is where we pull the IP information. Jeff, does this mean all L3 devices (each switch's upstream gateway) also need to be added in UDT?

Engineering is actively working on a hotfix. I would say days not weeks.

Thanks for being understanding about it. We'll get the issue into our engineering queue.

I'm sure it just got dropped in all the other issues being discussed since it wasn't directly related to the Case# 624 issue. I went ahead and have opened case #18199 attached snapshots. Problem is easy to duplicate. Thanks for your help and quick response Denny! Ron

is the difference divisible by 48576

Hi I added some more detail to the SQL, not sure if this is useful to anyone else. select e.ServerName, n.Caption, n.IP_Address, n.statcollection, n.rediscoveryinterval, n.nodeid, n.pollInterval, n.nextpoll, n.nextrediscovery, n.lastsync from nodes n join Engines e on n.EngineID=e.EngineID order by e.ServerName Kind…

 In your first image, it looks like you've specified an application name and then specified a component property. You want to specify the process name instead.

<throws bone> It'll be more of an 8.5. Not a major overhaul, but more than a couple off juicy tidbits. 

thanks, can this be done on a per site basis, and then scheduled to be emailed out say once a week? Manager wants this automated to show trends over last 30 days for each node....

Will agents be something that Solarwinds will look into?

It'll be in a future release. We don't deliver features in service packs, just fixes.

The Solarwinds profiler needs agents so that we can talk directly to disk arrays and SANs etc which is why i think Solarwinds will end up using agents. Microsoft SCOM decided to move to agents for unix and linux as we can't rely on what the agents tell us!

I found the solution. Open regedit. Navigate to HKLM\System\CurrentControlSet\Control. Add new DWord(32) with the name of ServicesPipeTimeout. right click on ServicesPipeTimeout and modify. click Decimal and type 180000 for the value. restart the server and resume installation.

My request to compute Days to Threshold was sent up the ladder so I do believe they care and that useful trending is something they are working on.

Cool, thanks for poking people :)

I want a notes field for nodes, interfaces, events, syslog messages so I can allow NOC staff to associate outages and ticket numbers this is a MUST HAVE. See this post: It might be relevant

 It has been released. If you are current on maintenance and it's still not in your portal, please contact Customer Service.