Donald_Francis

I think syslog is the best thing for that. But that is just my opinion.

We run netflow with about 250 interfaces and we slam the heck out of our SQL box and I suspect it is due to netflow. I would be very handy if it was a seperate DB so you could place it on another SQL box or at least on a diff set of drives. It would also be great if instead of their being a DB update for every flow if they…

Are you sure it is 3.5 or 4? I got this exact same thing and it was because I had a few boxes that were version 3. They do not support 3.

Just as an update to this thread as of 8.2(1)12 this issue has been solved. This has been confirmed.

hate to link and run but this should get you started. http://www.cisco.com/en/US/docs/switches/lan/catalyst4500/12.2/20ew/configuration/guide/nfswitch.html

I use syslog for this myself because you really need syslog anyway and its just easier :P

How is this? I am on a laptop right now so I had to kinda paste it altogether.

I would put your DB on a partition about 100-150GB. I have about 150 netflow interfaces, many of them 100mb-1gb or OC3 and T3. Our total DB size is around 60GB or so. We retain compressed data for 30 days.

I honestly do not think you could run all apps on one server unless you were monitoring like 500 nodes max or something. I run a lot of APM on one of my pollers along with about 4k elements for on it as an APM poller and it is the main box. Dual dual core server with 4gb ram and handles it fine. Of course I have 5 other Sw…

SolarWinds

That's a pretty good number. I would think it best you had at least 8gb RAM and a single proc that's at least dual-core.

No NTA has the same issue. They address ranges have to be contiguous. However you can label things the same and put in different IP address it will allow duplicate naming. But they willl still show seperatly.

I for one vote for no agents. Report Writer needs a rewrite. It is slow cumbersome and a pain the ***. The alert editor could use some love too but its not the lesson in pain reporting is. NUMBER ONE NEED IS A WAY TO MONITOR POLLING ENGINE STATUS !

- Flows between 2 nodes - Search a subnet at a time -Search in one direction (send or recieve) - Search by range of ports

I would disagree with that, I think one of SolarWind's strengths is that it does not need a client and through custom pollers can get almost anything from anyhing.

That's the portion of it I think is a bug. I had only about 150 devices selected within netflow but in spite of that its as if it was trying to pull stats anyway from ALL devices. I think all told it found 9000 CQBOS interfaces.

Something that the SolarWinds guys are not emphazing enough is the hurt it will put on your DB box. As they mention it totally depends on the number of interfaces sending netflow and how much data those interfaces handle but if its more than say 50 you are goign to see a serious increase in SQL server activity mostly in…

Maybe the answer is to possibly have an option that defaults to the Cisco default but gives you the ability to change the way Orion displays the detailed view of the interface/utilization per interface. That way if you are running per packet or per destination you will see the correct thing. The reason I am so adamant…

No question, you should use the full version. Even if you could get away with it now you may need it later. Moving it is not the worst thing in the world it would just be more to do.

To make it even more confusing it will actually enter the policy cmmand for you THE FIRST TIME you enter the destination command at global config. But after that you are on your own. Or that is what I have noticed after doing it several times.

I would like to see this as well. In fact I would go a little further. The current screens and graphs are great for top talker type of functionality, but I would love to see a different screen for more of a forenzic analysis where you can dive deelpy into a conversation or node and see all data related to it vs top 5 type…

So long as you have decent hardware you should be fine. I monitor many large chassis sitches with no problem.

I mentioned this on a post a few minutes ago, maybe it applies here maybe it does not. What if you use a loopback and assuming you have multiple connections advertise that loopback in only one direction over you link. When your link drops so does your route to the loopback setting a normal down node alert off.

OK so this just turned from frustrating to inescapably depressing. I was able to get this to work on the poller only install but I am rebuilding a web server now and I get the error regardless of the order. So this means I cannot install it at all. I figure there are is one person who is responsible for this. That would be…

Normally DBs are set to autogrow and SolarWinds DBs are also usually set the same way. So the first thing I would check is drive space.

The SW peeps will be political because they have to but I do not have to be PC. I think you are having an issue because your server specs are very poor. You are monitoring a good bit with very little CPU and RAM. Your DB server looks good but the other 2 especially the WEB box are aweful. You need more RAM on your boxes at…

There is an option to base line upon boot or wait a bit and do it in the background more or less. But to me your issue sounds like more of a performance bottleneck. Either at SQL or the main server. As I found out recently the more pollers you add and the more nodes you add to them cause a greater load on the main box. I…

I think it needs to be in more places than the Admin Guide. All the places you guys warn about backing up Maps and Reports I think that shoulds be there along side it.

Also I believe that "buffers tune automatic" is for routers only. If you look at the doc you will notice everything mentioned are router trains.