Donald_Francis

That would be one way but that would muck up my current group views and alerts. We use them currently for our highest priority alerts. The point to the suggestion though was to have something specifically for that so it could have it's own functionality. yes I just mentioned a simple list as an example but I should have…

Yes you are correct, for large chassis routers/switches which will typically be found in a core or an ISP. Getting a one stop shop quick view of chassis health (or even alerts based on it) would go a LONG way in heading problems off at the pass or troubleshooting issues when they come up. I have had several issues where I…

That config is for a normal router. A 7600 is more like a switch than a router and thus uses distributed processing. So I think you will need to setup NDE. Search for the netflow config on this site for a 6500. I think that will work for you since 7600's and 6500's are closely related.

Ethernet works that way when it is full duplex 100mb or gig but not data circuits or not any that I have knowledge of.

I have historically stuck with local only polling settings as every time I have tried poller bound something bad happens. And basically every time I put a ticket in for trouble with it I was advised to just leave it as local.

I would love to see the answer to this one from SW too, I have always wondered about it.

That is the default DOWN NODE resource with no changes.

I have not had this issue myself but I can tell you from experience sometimes less used MIBs on Cisco's end do not get the highest level of attention in every release of IOS. Also, what is going to make it even sillier is you are only monitoring the RP and not the SP, only half the game on a 6500.

It is probably because of a duplex mismatch, those types of devices are known for that. Often times they will only connect at 10 half duplex and with that many discards I would imagine yours have.

Actually it looks like it does indeed include traffic data. I did some captures and looked at the payload of the packets and saw traditional netflow. I would not jump ship yet I would think we should see it in NTA before too long, thats a total quess however.

Yea I am pretty sure for us its adding cores together as well as swap space and physical ram and comparing it to the physical ram amount.

I have asked for this in the past and second this. Bottom line if you are going to market yourself and sell yourself as an Enterprise product (which you are) then you need to support it like one. My company is a Fortune 500 and 100% relies on Orion for alerting, reporting, netflows etc ESPECIALLY alerting. We have been…

When I test fire the log shows it goes out as normal but I get the same results. One group can get them without fail and the others work here and there but usually not. 

Something must be wrong. No way you should even be getting the max. Protocol overhead and retrasmissions should eat away at the max pretty good. Also do not forget there is a difference between megabits and megabytes but I think you have denoted those properly.

That would be a horrible idea. You would compromise your DC and your NPM install.

I will add to that however that in the case of a DB box, you would indeed do it to protect the OS from the DB.

Ah ok, might be a GRE thing then. Probably the best thing to do is open a case with TAC I could see that being a bug or some odd limitation.

Jan you are correct. In fact I already do that. I was looking for something more out of the box and canned. For example when you look at the NTA summary of all nodes , having that listed next or under each node.

Each Solarwinds server that has the task to be a poller (does just what it sounds like it does) can poll max about 8k "elements". They all report back to the main server. But if you just had 2000 elements based off of 2000 nodes give or take 1 server should do it.

Actually from what I understand it is multithreaded. I know on all my procs I see even utilization.

 Thank you very much it is much appreciated. Just for reference to be clear. With 8.1 the change was immediate. As soon as you managed/unmanaged you would see the change in node details and on the next refresh of the web site. At this point it takes 30-60secs to see the change. For example you hit the manage button nothing…

I actually thought this is one of the things Flexible netflow solved?

How about number 5?????????? 5) Find a way to cache database updates so netflow does not beat a SQL DB like a rented mule.....

To the last poster. Syslog is great for that, and a lot of other things.

You also have your versions wrong. I do not mean to be a smarty pants I just wanted to be clear on everything and not have everyone confused. 8.2(1)-12 is what you are talking about not 8.2(12). The latest code is only 8.2(2)

What about seeing 6 instances of the job engine running, is that an issue? I have never noticed that before.

Have you checked with TAC on a possible bug? I monitor hundreds of Cisco devices with NPM and have never seen this.

Two things on this. First, if you are doing active/active NIC teaming on that server try active/standby. Also what might be the problem is indeed NIC drivers but not the one you are trying to ping. Broadcom (as far as I am concerned) is responsible for making drivers from time to time that do all sorts or horrid things.…

Never heard of this dying gasp but if you are talking about trying to find this info with solarwinds there is a built in alert for whether a node has been reset. An interface going down vs. the platform resetting is pretty different and could be monitored in a number of ways manually (SH VER) or through SolarWinds.

THere is no way for SolarWinds to do that really. The most accurate way to detect this is by looking into the mac-address/arp tables of your switches and see what they report as the mac of the particular IP. If the mac changes you know you have a conflict. You can just ping from your switch the address in question and look…