mcbridea

The configurator won't work on a 6500. You will need to config by CLI

This feature is on the roadmap. No date to share right now.

Also check out this thread where a community member has posted a work-around.

If you have other SNMP tools on that machine chances are the SNMP ports (161, 162) are taken by those tools. if you shut down the other tools, make sure they are not set to autostart then stop and restart start NPM services from All Programs -> SolarWinds Orion -> Advanced Features -> Orion Service Manager. If it still…

What are you using for storage on the SQL server? Is it a dedicated box or a VM?

Use the trigger condition "last boot has changed". This is done by selecting the Has changed conditions.

In the Control panel -> Add or remove programs

Hey Dallium, I can't fix the work environment but apply SP1 if you have not done so. Andy

Hi - I saw this come in as a feature request in that forum and have marked it for PM attention. Thanks

That will work for a small evaluation only, XP is not supported for a production deployment.

Go into Transform Results Wizard and on the Formula screen there is an Add Poller button.

IP SLAM does not write to start up config. If a device reboots IP SLAM sees the missing config and replaces it. This is only true if the IP SLA operation was created in IP SLAM.

I don't know of a way to accomplish that one, but I'll move the thread to feature requests.

Do you think this KB may apply? http://support.solarwinds.com/kbase/ProblemDetail.cfm?ID=1323

I'm not sure what you mean by incoming IPs. If you mean public addresses you could create a public addresses IP Address Group and then use a canned top N by address group report.

I believe the built-in APM Current Status of Components report will do this. It is actually a "last 30 days" report but you can change the time frame.

The transmitters and receivers would be the same regardless of ingress/egress.

You will have to keep some data but you can minimize it by going to Admin -> APM Settings -> Data and database settings. Try setting all of them to 1 day. Keep in mind this will impact APM reporting for any time period greater than "Today". You will also need to modify or delete any APM resources with a time period greater…

Hi Drew, This is a known bug we will be releasing a fix for soon. Andy

Looks like that could be a bug. Have you opened a ticket on it?

Hi Mine, I have not seen this issue before but support probably can get you moving along if you open a ticket. Andy

Hi Jordan, We rarely get anyone asking for NetFlow v7. Andy

Did you try View Limitations in Customize Page? There are several options for eliminating devices.

A couple of questions to make sure I have a clear picture of what you need to accomplish. The 3 qualifiers you are using, remote-server-1 is down IP Address is equal to 192.168.7.2 Node Status is equal to Down Are these intended to apply only to one server named remote-server-1 with an IP address of 192.168.7.2? If so,…

Can you add a drawing so we can see the details?

Use the Group Member property type and Member Status is equal to Down.

Presently ports that are part of a group will not report outside of that group. So if 8080 is part of a group this is the cause.

Not today

You can't change the property type when creating an alert, it breaks the alert. The best way to approach this would be to create a Custom Property and mark the entities you want to include in the alert. Custom Properties are supported in all alert property types.

Hi Mark, The VoIP settings wizard will help you set up IP SLA operations. All you need to do is make sure Orion NPM has the read/write snmp strings for your IP SLA capable site routers, add the sites in the VoIP wiward and then specify which site is the hub. VoIP will automatically set up the IP SLA operations. Andy