JasonFerree

This article may help http://www.cisco.com/en/US/docs/ios/ipsla/configuration/guide/sla_udp_jitter_voip.html IP SLA manager doesn't really calculate the MOS score. We just take it from the device. On a network that doesn't have issues, and using the same codex I would not expect the score to change much.

Ok, that should be fine. The best thing to do then would be to submit a ticket. We'll have to turn on some debugging and collect some logs. http://www.solarwinds.com/support/ticket/

I suspect that there is actually another alert that is causing the message. We would need to take a look at a diagnostic to take a closer look. Can you open a support ticket and reference this thread?

Ya, looks like the view is either set wrong or has somehow been reconfigured. Did you check your account settings? If so, best to open a support ticket and reference this thread. http://www.solarwinds.com/support/ticket/

The TNS names file is on the Oracle database. If you are getting that error it generally means that the Destination point type and point name are not configured correctly. You need to look at the tnsnames file on the oracle server to configure. This should help:…

FYI: There is a very easy way to do them all at once (or at least large chunks at a time). On the web page goto: Admin manage nodes in the group by select SNMP version - this will regroup them by their snmp version. select the ones that are a (1) click the box at the top - this should check all the nodes click edit click…

Also, pass me your case number so I can have a look at the netflow issue.

It goes back to what qle said. Do you get events in your windows event log that would tell you if a failover happened?

Because the source and targets are not the same, it's not really the same operation. That's what is going to make it tricky. As for the responder, that's just a simple config command to turn on the responder on the target machine. IP SLA manager should also be turning this on for you if we have the RW creds to the target.…

Orion does not need to have the RW strings. You can walk through the IP SLA wizard and select "Monitor existing operations". If you are going through the wizard and you select "Create New Operations" then Orion will need valid RW community strings. If they are not valid or the device is busy, it could prevent IP SLA…

There are a lot of files, too many to list. Both APM stand alone and NPM stand alone share what we call Core services. When you install NPM and APM on the same server the Core services are the same and the 2 products merge. It is expected for the configuration wizard to state that the same site already exists, you would…

This is the Success Center doc for the NTA 4.4 NTA 4.4 System Requirements - SolarWinds Worldwide, LLC. Help and Support

Thank you for sharing your feedback. Our phone queues are our number 1 priority. The last thing we want is for our customers to wait on hold. Also, your online tickets should never be ignored. I would like to investigate this further. Can you PM or email me at TechnicalSupportFeedback@solarwinds.com your SWID or case…

Hello, It's called a Windows service monitor however it can monitor any service on a Windows server. The name is trying to focus on that you can use this on a Windows server. Take a look at this page from the admin guide. http://www.solarwinds.com/NetPerfMon/SolarWinds/OrionAPMPHComponentTypesWindowsService.htm

There is, but you have to enable it. Here is how http://knowledgebase.solarwinds.com/kb/questions/2431/How+do+I+turn+on+debugging+%28Monitor+Probe+logging%29+for+Orion+APM+when+requested+by+Technical+Support%3F

Hello,Most commonly customers will set up 2 alerts. One for when the service goes down. This alert will be based on the status of the component such as up or down.One for when it goes warning or critical. This is based on the thresholds that are set for the component. If you only want to be alerted when the component goes…

Hello. When IP SLA manager sends operation config changes to the device it will only add the config changes to the running config. They are not saved to start up. If for some reason the device is reset and the running config no longer has the IP SLA operation config changes that were automatically added when you did the…

This tells us that the 'MSExchange ActiveSync' performance counters are not installed on the target machine. In order for APM to be able to poll specific counters they have to be available on that box. Chances are if you look at perfmon on your exchange server you'll be missing that catagory. Either they do not apply for…

perhaps the "Log Source"?? Log SourceEnter a log source to further restrict the match criteria or leave the field blank to match all possible log sources.Examples of sources are Service Control Manager, Microsoft Office 12 Sessions, ASP.NET 2.0.50727.0

If you use the "Find" wizard select services. Then scan the target node in question. You should be able to select the services you want to monitor. This will tell you if they are up or down.

Try these: http://www.solarwinds.com/NetPerfMon/SolarWinds/OrionAPMPHComponentTypesWindowsService.htm http://www.solarwinds.com/NetPerfMon/SolarWinds/OrionAPMAGCreatingNewTemplates.htm the easiest may be the Find Processes, Services, and Performance Counters wizard mentioned in the last link.

It may be an offset between the time zone that is set on the device and what is being used by the Orion server. You may need to add the time zone code that is configured on the device to match what is on the NPM server. To do this modify the ipsla.timezones.xml file located in the C:\Program Files\SolarWinds\Orion\VoIP…

The host name should be taken from the node assignment so you shouldn't have to specify it in the component configuration. You assign the user experience monitor to the host name. Inside the component details you should only need to specify the instance name.…

The status message should tell us why it is unknown. Then we know the direction to troubleshoot. However, does you alert trigger when the component "is equal to down" or "Not equal to up"?

Are you creating the operations manually on your devices or are you having the IP SLA manager create them for you?

The snag you are going to run in to is the process will sometimes be down. This may be expected, but in APM, the process is down and will be marked as down. Once this happens the whole application template will be marked as down. We can't ignore it because we are supposed to tell you that it is down. Unless you unmanage…

Hello, There are come default UDP ECHO reports built in. Have you tried starting with these and customize from there?

hello, The "has changed" is reserved for alerts such as last boot. You can’t use the “has changed” for alerts related to APM. You may want to try something like is not equal to up. This would give you the unknown events.

Log file is stored: C:\ProgramData\Solarwinds\Orion\APMServiceControl.txt Also, ensure that component 4186 is a windows service monitor.

Hello, Operations are only created on one side, the source node. If you want to monitor connection both directions then an operation would need to be created on both nodes. Therefore you would have 2 source nodes and 2 nodes would count towards the license. Once the node is a source node, you can have as many operations…