rob.hock

Generally this would point to a windows or other software firewall issue. Try disabling the firewall completely (if possible) to troubleshoot.

You may lose a few hours of historical data and have some bogus alerts for a few minutes when it comes back up, but going forward there should be no issues. It would be advised to stop Orion services before making the change.

Interesting issue. Could we perhaps upgrade the second console to 9.0.1 and retest?

We did create some new pollers for Fortinet in NPM 11.0 that match on SysOID. May need to be adjusted for additional models. Check under Settings->Manage Pollers

If you check out the beta for v12, 4551's should be properly recognized: NPM 12 Beta Survey

The upgrade process is indeed supposed to migrate macros to the new format. Is there a support ticket number we could reference for follow-up?

Not a known issue- a support ticket may be the best course here: SolarWinds Customer Support - We're Here to Help

What features of Notepage are you looking at that are not inherent in alert manager?

If you upgrade to NPM 10.7, this functionality has moved to the web- thus addressing by default.

The migration guide explains this procedure in depth: http://www.solarwinds.com/documentation/orion/docs/OrionServerMigration.pdf

If you access the DB directly, the below SQL query will reset the admin password. Update TECH set user_name='admin', password='admin' where client_id=1 If you are using frontbase this FAQ will help you connect: http://support.webhelpdesk.com/cgi-bin/WebObjects/Support.woa/wa/FaqActions/view?faqId=5

Rob, At present no- groups were the answer for this sort of use case. Perhaps there is another place (Network Atlas map perhaps) that we could convey the same info in some way.

That seems pretty textbook. May want to recreate the dependency to be sure, but otherwise involve support: SolarWinds Customer Support - We're Here to Help

There is no method at present, however if you set the default zoom level to be a bit tighter, they would appear smaller relative to the geographic area.

Likely culprit would be interfaces reindexing. Juniper had a historic issue with this pre-JunOS 10.1. (Junos OS SNMP FAQs - Technical Documentation - Support - Juniper Networks) Reboots and upgrades caused interface re-indexing.

Is your NetApp is able to receive syslog, or were you looking to somehow export messages to a CIFS share on the NAS?

Would depend on your requirements, but at a minimum you would want to park your license. Sounds like you have already done so, but just in case migration guide is found here: http://www.solarwinds.com/documentation/orion/docs/OrionServerMigration.pdf

Thank you for your interest in the beta. The survey link is the same across all betas: NPM 10.7 Beta 4 Survey Please let me know if you encounter any issues, otherwise we'll get the beta over to you straight away. Regards, Rob

10.7HF2 is a stand-alone HF targeted to 10.7. You would need to upgrade to 10.7 (using the full installer) first, then apply HF2. Please let us know if you encounter any issues.

Are you looking to restrict the account to a set of nodes? A Multiple-Object-Chart or Custom Table resource could also be used depending on what you are trying to accomplish.

Believe that's populated from the interface speed either auto-detected or manually set:

Thanks for the feedback. Yes, migrating applications to 64-bit is an ongoing process. (See what we are doing with the latest version of NTA.) Believe it or not we still have a lot of customers on 32-bit for one reason or another. The Orion platform is multi-threaded to such a large degree, that the performance gain from…

Perhaps a backup made at some point? Check your active DB under settings / DB Details.

Negative, that is definitely an odd issue. We should probably have our support team dig in on that: http://www.solarwinds.com/support/

Were you able to find the appropriate OID for queue tree values? You may have come across this already: http://www.mikrotik.com/testdocs/ros/2.8/appex/mrtg1.php

If we deploy sensors to the endpoints (or add them to an NPAS) then yes, we can get granular endpoint statistics. Check out this post for more information: NPM 11 - Packet Analysis Sensor Deployment Considerations

If the polling account is passing validation, we should be communicating successfully with vCenter. A support ticket may be the way to go on this: http://www.solarwinds.com/support/

If you upgrade to 11.5 - we have the ability to modify individual sensor status / thresholds.

Thanks for trialing sir! Currently Wireless Heat Maps are supported with modern Cisco WLC. We're looking at expanding support to other vendors for the future.

Those look like SWIS timeouts. The causes could be myriad, but I'd look at DB performance first. Support ticket may be the best course of action: SolarWinds Customer Support - We're Here to Help