bshopp

Interesting, for sure would recommend opening a Support ticket to investigate further

brock, I just looked up your case and the associated case in our tracking system and this appears to be resolved in the next release, I will reach out to you offline to discuss further.

Sorry Byron, I am checking on the status of this. The dev folks are focused right now on wrapping up a dev iteration so we can get beta 3 out for NPM.

Never give up, even though sometimes it may take a little while to get into the product, we are listening. This feature was included in 10.1. We just have a lot of stuff on the list, we get tons of feedback on thwack alone, along with the conversations myself and the other PM's have here with many of you.

If what support gave you did not work, I would re-open the case with them so they can track the issue

Another option, which is I am not saying is ideal, is if you have good SQL skills, you can create advanced SQL alert, which was added in NPM 10.1 on the CustomPoller* tables with “Custom Node Poller” and “Custom Interface Poller” trigger types. It may have to be very specific, but should be able to be done by joining the…

On the first item, right now the color coding is based on subnet usage, I will add an enhancement to the system. On the second item you can do wildcard searches from the IPAM Summary Home page or from the Manage Subnets and IP's page as well. Is it not working for you?

Product Manager here, I am looking into this and discussing with R&D, stay tuned.

Please see this post

We were very dissapointed as well when we got the vSphere 4 Beta in our lab and identified the issues and lack of SNMP support (which as I inidcated they removed) and we reported this to VMWare. However, by that point in our process of the release, it was to late to address. It is a high priority for us going forward as I…

Stand up a new VM or server to run the beta on. You leave your current production server alone, we do not support running beta on top of your current production install. It is basically having another Orion server hitting a portion of your network and you give us feedback, point out the bugs etc. and help us shape and…

We released 10.1.1 SP1 today, focused on polling performance. It incorporates HF2, however, if you care and need HF1 you will need to re-apply after upgrading to SP1.

See here for what is currently being looked at for the next release

I would add the hotfix #2

Did you run the item specified by Karlo above in the thread so you can start monitoring them? Yes, this will be fixed in an SP

I would recommend a support ticket, or upgrade to the 10.0 RC and see if your problem persists. If you have active maintenance, the 10 RC should be in your customer portal

Yes, you need to run them still

It should work, I would open a support ticket to investigate further.

We will have something that can be tested with the next version of Orion, but no timeframe I can really give you on beta other than second half of this year.

Awesome, glad to hear this issue is resolved for you!

I got it logged in the system, thanks for the post

Very very soon, it is validation right now

What is the current Orion version you are running on?

Maintenance gives you two things * Product Fixes and Updates * Support Here is what we are currently working on right now - I have some thoughts on what I want to do after that release, but would love to hear your thoughts as well.If you are interested in the RC for the release we are working on, let me know and I can add…

All, per my post yesterday on this topic, please see this new post - 

Let me contact you offline to see what you are seeing. If you remove/delete them from the subnet, they should not count against your license count.

All,I just wanted to post a quick response regarding this item. Our intention has always been to license by Managed IP and during the Design and Beta phase we went out and vetted our approach with a set of customers. It has become clear based on the feedback of customers and the community that we don’t quite have it right…

Seems like something might be off. Can you cancel the running jobs and submit the job again?

Support will be able to help you, if it is the issue I think they have some scripts for you to run on your DB

To add to Andy's comment, sorry for the confusion on this. As I mentioned we are working on fixing the known defects and when we release the next SP we will post the list of variables again. I cann't give a timeline when the SP will come out