mcbridea

That is telling you that the device does not have 64 bit counters for the interface OIDS, or at least that something is going wrong in accessing them. Can you do a MIB walk on the device and see if it returns the high capacity (HC) interface OIDS? If you don't have a MIB walk tool you can DL Engineer's ToolSet and run it…

Follow these steps * Open Orion Custom Property Editor All Programs -> SolarWinds Orion -> Grouping sand Access Control -> Custom Property Editor * Click Add Custom Property * Click Add a new Custom Property from scratch * Select Add properties to Interfaces * In Property Name type IsWAN (exactly as shown) * Property type…

I see. That template is a flexible NetFlow implementation and won't work unless you also match ip source, ip destination, tos, input interface, destination port, source port. The default template for v9 includes these but I'm not sure how that is implemented for the 7K. For other platforms you just don't specify a template…

I think support will have to tackle thois one.

Do you have nodes that have the CPU being monitored? Normally a missing option like this is because that entity is not in the database. If there are nodes with monitored CPUs please open a ticket so we can investigate.

Can you post the alert trigger?

Did you get a chance to look at that paper? It has a method that I have tested and it will do what you want, but I recommend deviating from the method shown as little as possible. .

Do you consistently get one specific result for using the GUI and an other specific result using the copied SQL?

A packet captur off the NTA server would be golden.

* Change the syslog retention to 7 days * Run database maintenance * Set up alerts on critical disks

Are the group status roll ups all the same? (Best, worst, mixed)

Have you checked out the IP SLA ICMP path feature we released? It does exactly that.

That polller points to the Cisco NTP OIDS. You might be able to replace that OID with the host one but I have not tested that.

Yep At&T should be able to help you

Hi Julian, Adding more vendor support is high priority. I am considering adding Procurve along with several others. Andy

10.2.allows sub-minute polling. SNMP timeout won't help.

Check these papers as well. http://www.solarwinds.com/documentation/Orion/docs/Groupsanddependencies.pdf http://www.solarwinds.com/documentation/Orion/docs/UnderstandingOrionAdvancedAlerts.pdf

Can you expand the NetFlow/IPFIX (last) area of one of the packets and post that? Also make sure you have the template timeout set to 1 min in the config (config)#flow-export template timeout-rate 1

Thanks for posting the fix!

Thanks for posting the solution!

It is a bit confusing. I'll see if we can clean it up. Andy

Yes - it needs to be on the main Orion.

You can access more total memory for Orion, the OS and anything else running. Also 10.1 pollers take advantage of multiple cores.

There is a canned report called Historical Interface Errors. You can modify this to include errors and discards on the interfaces you specify. This doc should help as well. http://www.solarwinds.com/documentation/Orion/docs/UnderstandingOrionReportWriter.pdf 

I'll enter this as a feature enhancement. Andy

OK. Can you tell me exactly what you have done to this point? How did you change the URL?

The alert looks good. Are the links down for a long time when you see this or does it miss short outages? If it is missing short outages you could flip the second condition to - Node status not equal to up -

I'm not sure exactly what may be causing that. I'll see if the dev dude can chime in.

No problem. One note, if the device or interface is layer 2 only then some of the required fields will not be defined, so we will drop the flows.

"UDT and Orion NPM must be installed on the same server using the same database" You could use seperate servers and seperate instances of SQL, but you will not be able to use one web address to access both. They will not integrate.