mcbridea

It looks like that is working using .6 on UnDP. I scanned through support cases with a "No such name" error and it looks like that error is pretty generic. Can you open a ticket for this issue? http://www.solarwinds.com/support/ticket/supportticket.aspx

Can you post a screen shot of the alert trigger?

OK - those are Orion views. I'll get with the Orion PM so that I don't tell any lies here. ;) Andy

The upgrade will stop and start them automatically, but I always stop them in Orion service manager as a precaution. I also check after the upgrade to make sure they all are running.

Can you do a MIB walk and see what the Interface status OID is returning? Also, what type of devices are these?

Were doing some internal testing on a new feature set but no beta right now.

It is hard coded

You would need to edit the built in advanced alert for packet loss. The screen shows 1% loss so you would need to set the trigger level to "greater than 0". This is a very low level and may result in a mass of alerts.

Cool - hope it works for you. I suggest sorting things in content exchange according to downloads, this bubbles the better ones to the top.

You'll have to go through and remove the sources that were automatically added.

That feature was needed some more tuning so was not released in 3.5. We are still looking at the best way to accomplish this.

Pryo - That's cool! Can you export that poller and share it in content exchange?

That is a good workaround but the request is to put those in the drop down.

http://www.solarwinds.com/documentation/IPSLA/docs/IPSLAManagerAdministratorGuide.pdf See appendix B

Just to clarify, we do not support IPSLA inside an MPLS network. You must apply IPSLA to the CPE (MPLS edge). That is where you can specify which VFR to use in the IPSLA manager wizard.

That is correct

Thanks for the quick answer! I see there is an option for Routing, but not topology. I'm guessing these are one in the same.

For NetFlow realtime only version 5 is supported. NetFlow Traffic Analyzer module supports versions 9 and 5.

Thanks Jiri. I'll take your advice and add a few cores as well.

To clarify, the Syslog table can be truncated if your internal retention requirements allow it.

Note the change to the above post. You will have to use a custom property to accomplish this. Here are the steps: * Create a Yes/No custom property called Building 1 (or whatever you want). * Assign the property to the nodes in the remote building * Edit the alerts and add a simple node condition Node ->Network Nodes ->…

I don't know that this can be done. Did you create a Undp for this? If so, can you share that?

Thanks for taking the time to post. I just wanted to make sure I understand where you were looking as there are similar drop-downs in other parts of the application. The "not equally to" option is not included in this area. I will mark this for a PM to look at and see if it can be considered as a feature request. It helps…

Yes - that was quite a few hubs! Glad to see you found the solution. Andy

Thanks for pointing that out - We'll invesitgate and fix. Andy

Hi Guys, This is a known bug in 3.0 and we are addressing it. The flow correlation table will rebuild so no history lost. Andy

Also see this thread

Hi Freeman, Not too sure what is going on with this issue. I suggest opening a ticket and support can help you through it. Andy

This paper may be helpful. http://www.solarwinds.com/documentation/Netflow/docs/NetFlowTroubleshooting.pdf

thehirchuk, Can you repost this in a new thread? This thread is more for customization sharing than how to. You will have a better response that way. Thanks - Andy