mcbridea

If they are truely duplicates then yes.

Looks like the Rec bps = 0 and rate> 0 conflict logically. What does rate refer to?

Are you on 3.0? If so can you attach a screen shot?

Looks like a ticket will be required.

Table JOINs are used internally in NPM but not a feature of UnDP today, which probably is where you need it.

Cisco books has an MPLS Fundamentals book that is quite good. ISBN 1-58705-197-4

Yes. If you have rapid wraps then that is a good reason to poll more frequently.

Hi Don, The hot fix is out but it addresses problems with plain text alerts. For this one, I suggest you open a ticket. If you post the ticket number, I'll follow it and document the solution for others. Andy

Just to clarify, SolarWinds does not create custom SQL reports but we encourage our SQL saavy members to help out if they can. Any SQL gurus need some good karma?

Discards happen because the device cannot do anything with a packet. This can be because the device does not have a route to sent the packet to the destination, the device has been configured to discrad certain traffic or the device lacks resources to do anything with the packet (such as full buffers). To some devices have…

My mistake - License manager is only available in Orion 9.0 and up. To check your license before 9.0 you have to call customer service. I guessing that you may have inherited a license mismatch.

OK - I'll look into why the responder port is opening and if we can configure to eliminate that.

Hmmm. I would try a show ip cache verbose flow and look for the traffic there. If it is there then pcac on the NTA box and see if it is making it there. I assume that there is a direct path between the remotes. Also note that if any of the traffic is MPLS labeled traffic NetFlow won't see it.

Plaease open a ticket on this one.

Hi mbwalker, We fully support IPFIX as of NTA 3.5. Andy

Open a ticket please.

Yes, that does make sense. I would create a group for those key devices and then place a group resource on your home page via Settings -> Manage Views. Once the resource is on the home page click on the resource Edit button and make sure Remember Expanded Groups is checked.

That is the chart I thought you were refering to. It is built from the ping responses. The NPM server pings the managed devices and the devices reply. The ping response time is shown.

Justin, I had QA run extensive tests on this and they found that the Orion 8.5.1. IF data total and NetFlow v3 data total for the same IF were dead on. There may be an environmental issue. causing this. Also make sure you have all applications and ports monitored. Andy

I suggest you post in the feature request area for NPM. http://thwack.solarwinds.com/community/network-management_tht/orion-network-performance-monitor/orion-network-performance-monitor-feature-requests

I don't believe you can do that today. I'm researching a solution for this one.

Latency and jitter will work fine. Those are accomplished using IP SLA operations. What you won't be able to see is call manager specific information such as registered phones.

I hear you guys. These are all options we are considering. Andy

Hi Donald, We are investigating ways to off load some work from SQL. No Dates to promise Andy

Hi Kevin, It is available now. http://www.solarwinds.com/register/registration.aspx?program=945&c=70150000000FBRJ Andy

Hi All - We are looking into this.

You could do that but I don't get the point of why you would. If you are going to measure 1 MB of pings why not just measure the transfer of a 1 MB file? ICMP never carries user data so you would only be measuring your network's ability to move pings.

Yes, but I believe it is more an industry standard rather than an Orion thing.

Orion uses MS SQL as the system database. Chapter 2 of the NPM Admin guide outlines these requirements. http://www.solarwinds.com/support/Orion/docs/OrionAdministratorGuide.pdf Let me know if you need further help - Andy

Actually taking another look at the drawing I'm not sure what the multiple router group will accomplish. If one of them goes down you probably don't want to not see problems with the rest of them. If there are multiple connections between level 2 router and switches I would group according to that. Put everything below the…