bshopp

When you rescan, you only need to import one single element, a node, volume etc and the topology DB will be updated. When you try to import it, you will get a message that element already exists in the DB and does not change any of it's setting etc.

I have seen many deployments. A lot depends on the skill set available in house. Ex. are you working with your DBA's or do you maintain Orion DB yourself. NeverFail who we partnered with have an offering just for the Orion DB, see here.

How did you try doing this? If you go to web node management in the web console and select one or more interfaces, you should be able to select unmanage now in 9.5

I would recommend opening a Support ticket on this issue

This does appear to be accurate, we can ping it, so we can give you only node availability.

It depends on which RC you upgraded to. RC3 ended up being the GA build so if that is what you upgraded to then no. If you were on RC1 or RC2 then yes you need to upgrade.

Scott, I have not seen this or heard this from others. When we log in via AD Groups we create a virtual user on the back end that get recycled/removed when session is completed and we re-check next time they login where that user should be places. I think a ticket is warranted here to dig into further.

Good feedback, on #2 can you describe more what you are seeing? #3, we already have an enhancement logged in the system and #4 is high on our priority release for a future version.

Hard to diagnose with such limited info and the error code is generic, just means application exited unexpectedly. Are you working with a sales rep? From the win32 under File, you should be able to create a diagnostics file which we can use to troubleshoot this further. You can attached to this thread or send to your sales…

I spoke with Dev and confirmed we do not do this today. This is due to the fact that after syslog service restart all the message queue value will get reset to default value.

I don't believe this is possible, but I will double check with R&D.

Can you tell us what version you are getting this error on?

So you can't join together two tables today in a single UnDP.

What do you want to monitor? I am guessing Orion APM, which you can read about here will do what you are probably looking to do.

We are working on something that will do exactly this, but it is not in the version checker utility, but in the web console

If you go to Admin -> Manage Views you can create any custom views you want

Have you read this here

At a minimum, NPM will allow you to monitor those devices for fault and performance and alert and report on that information. Beyond that depending on your needs, you may also want to look at APM for deeper application monitoring, you can read here

Nothing native no, but can you export to csv or file the IP's you are managing in Sentry and then use those in the bulk upload option of Network Sonar?

So when you drilled down you would drill to a map? Have you thoughts about creating a custom HTML resource?

9.5 no longer support SQL 2000 and Windows 2000, so make sure your OS and DB are at correct levels

Orion 9.1 does not support SQL 2008. If you want to upgrade to SQL 2008, you will also need to upgrade your NPM to 9.5

Can you explain a little further what you are looking to do please

Do you still need them or did you figure it out yourself?

I created a defect on this. Potential workaround: If you create multiple discoveries, you can have the same username with different encryption methods. Depending on the size of your subnet list, it may be a pain to keep two in sync, but it will allow you to get around this.

I have not heard of any other reports, please open a support ticket to investigate

So for controllers we only support Cisco and Aruba currently. If they are thick or autonomous AP's, if they support the 802.11 MIB they should work.

Can you provide a little more details around what you are attempting to do?

Did this just start when you upgraded to 9.1 SP3? I would recommend opening a support ticket and include diagnostics to further diagnose the issue

What version of NPM are you on? In 9.1 using web node management. In Admin, go to Node Management, group by location, select the location you wish to update, select the check box to select all and click edit and then update the Polling Interval.