chris.lapoint

Are you using the TFTP server included with Orion NCM or the free version?

Can you try disabling node monitoring / rediscovery by navigating to File > Settings > Node Monitoring? If this seems to resolve the performance issue, then your the problem you're experiencing is a known issue that we're working on resolving in SP1. It would be really helpful for us if you would open a support ticket…

That's good news NickG. Did you simply add the monitor manually or did you get the discovery working?

First of all, I absolutely agree it shouldn't be this hard and we're working to resolve your issues. The error your are receiving is due to a known issue (see release notes), which occurs when adding NetFlow-enabled routers with noncontiguous interfaces. We will have a 9.0.1 patch release out very soon to fix this problem.…

This is indeed strange behavior. Do the values eventually reappear on refresh or are they always missing?

We're going to look into this.

Please try setting the Inventory Engine settings to allow more concurrent processing and let me know if that helps. You can access this setting from File > Settings > Inventory Engine.

We're working on an updated Log Forwarder beta version that includes: * Support for Windows XP/2000 * Support for Vista/2008 * Fully extensible filtering of Events * Silent install support using MSI (e.g. for use with Microsoft SMS) If you're interested in participating in the beta, please sign-up here:…

jcooler, if you stop the service, then that effectively stops the indexing process. You'll need to start the NetFlow Service and leave it running so it can reindex the tables. You should see status of this process in the Orion website. NetFlow collection should begin automatically after this process completes. When you…

We are definitely looking into making more config details (e.g. interface/port) available in the node selection criteria. I can't commit to this being in the next release given the resources we're putting into Orion integration and Cirrus website, but we'll definitely consider it. Wrt/ to multi-line RegEx, a customer I…

The problem is the NPM node ID isn’t going to match the NPM node ID since they’re separate databases. If you want the job to be dynamic, you’ve got a couple of options: Option 1: * Create custom property in NCM called “Include” (or something like that) * Create an NCM job that targets all devices with “Include” = 1 *…

Thanks for the feedback. We'll definitely look at including out of the box reports moving forward.

Also tried using direct telnet & SSH using putty and it worked fine. This verified that my TAC acct used by Cirrus was not locked out and still working outside Cirrus. At this point I'm stuck. There should be no reason why the report is giving me this error, so onto a ticket. I'd recommend upgrading to 5.5.2. We added…

That seems like strange behavior to me. Please submit a ticket with your steps and we'll try to reproduce in-house.

PLEASE NOTE: If you reply to a post notification (communityteam@solarwinds.com), we will not see your post. Instructions on setting up Realtime Change Detection can be found in Admin Guide (p. 47): http://www.solarwinds.com/support/orionNCM/docs/orionNCMAdministratorGuide.pdf

What version of NCM are you all running? NCM 5.5.1 includes a scheduled Orion NPM node import job (Schedule > New Job > Import nodes from Orion database). The job allows you to filter nodes imported based on Vendor and Machine Type.

That's not correct. Your NTA license is based on your Orion NPM license size - this is best approximation we have for the traffic analysis value received since not all interfaces are created equal (e.g. WAN interface versus internal switch interface). So, your NTA license allows you to collect NetFlow from any of the…

I don't believe we were ever able to isolate this to an APM issue versus an issue with that Windows OS version, especially since only a small handful of customers are experiencing this behavior. Please open a support ticket on this issue so we can investigate further. Thanks,

To accomplish this today, you'd need to schedule the devices in separate jobs and stagger them appropriately.

That's correct. ipMonitor is intended to be a quick and simple, all-inclusive but entry-level network monitoring solution. If you are looking for something more extensible/scalable, then you'll need to consider Orion.

5.5.1 is a full upgrade and is available from the download page (the release note indicate the version of the download). The zip file should include the server upgrade as well as the integration module upgrade.

This is NOT possible today, but we'll definitely keep this on our radar.

Just to close the loop, we've been working with this customer offline and have provided a patch that we believe has resolved the original "hanging" issue. If you're experiencing similar issues, please contact support.

We'll definitely get you running with your config change report, but is there a reason you're not using the config change notification built into the backup job? This is what most of of the customers I've talked use quite frequently for the use-case you described.

We're updating as we speak. Please check back later this evening or early tomorrow morning.

If you downloaded before 11/10/2009, please download the latest version from the customer portal (download will say v1, but the install executables will be labeled 1.1.13). This new release should resolve your issue. If it doesn't, please open a support ticket. 

actually, looks like your content sharing zone post went through. Did you experience errors when posting?

There are two credentials that must be discussed here: 1. Credentials used by the Job to run the task through the Windows Task Scheduler (logs into Windows OS). This should be set to a service account that never expires 2. Credentials used by the Job to login to the devices when the "User" option is selected for Login…

Nailed it.