bshopp

Yes if you go back into the portal, I believe this should be fixed and updated.

Thank you for flagging and raising this up. That date is on the full offline installer should be correct and the portal is showing the base release date for 2020.2.1 which was August as you indicated. We are working to get this addressed now. Thank you again for flagging this.

We are actively working on this. I am soon to be scheduling some user feedback reviews with customers under active maintenance to get feedback on what we have done. If you are interested, I will make sure you are including in that. 

Be an existing customer on maintenance, have a non production box we can install on and your time to kick the tires.

We are working on it as fast as possible. Changing the method of gathering this data from SNMP to API is not a simple change. There are a host of things you have to change to adopt this, such as inputting API credentials and managing those securely as one example. We would love to have you participate in the Beta/RC…

Have you changed the group by to only see autonomous access points and not controller? When you drill into the node details page are you seeing any AP info like connected clients etc?

Can you please open a support ticket and please reference this thread

All, we have released SP3 today, please see this post for more information. We have confirmed that SP3 does fix many issues including what many of you have reported on this thread. However, as you can see from the last couple posts, we have come across a couple instances in which there is another issue and we are working…

Can't give you dates on the next release, sorry.

So we are going to be doing a small beta on ESX, so if you are available next week and interested and have a spare box to test on and are under active maintenance, please PM me via thwack. We are only taking a small number, so we may not use everyone that contacts me

Just pinged you both offline via email

I will contact you offline and we can setup some time to chat

AnbanyNY, please contact support if you want to get the SP to see if it resolves your issue

We made this change in the next release of Orion, just an FYI

You will need to contact Support

Dave, Fair question. By the time we learned from our internal testing of the ESX4 beta and from talking with VMWare that they were partially dropping their SNMP implementation which we used, it was too late to do anything about for 9.5. I think the fact that we are able to switch around our roadmap based on priorities from…

Jeff, have you opened a case and uploaded Diags?

Everyone who has requested access to the RC here should have been added, if I missed someone let me know please

This enhancement was just entered recently, so unfortunantly it came in too late to include into the current release we are working on, so we will consider it for the next release potentially.

One idea one of my esteemed colleagues just pointed out to me which might be something interesting for you to look at, with toolset 10.4 the integration with Orion has been updated to include workspace studio which has a topology gadget in it, see here for more details

Couple ideas to throw out, you could cron a script to take the values from the other DB and insert into the custom field in Orion. You can try and see if you can get it to work in the custom field by putting an href html link tag, when I tried it it did not work for me

Right now, just delete the controllers, we are working to address the license issue, that is a bug

Good to hear on the SSID, I am investigating on the client name and have already contacted you offline to get some additional data

We are about to ship a 9.5.1, which rolls up some bug fixes and enhances performance of the "job engine", which runs UnDPs and some other polling. After that, we'll have a more substantial version coming, which includes the VMWare stuff. It should be available as a release candidate soon, but I can't be more specific than…

In the first item, I am working with R&D on formally addressing, but the workaround is the following. Manually edit the CFG file and change <keywords> <string>Audit Success</string> <string>Audit Failure</string> </keywords> To <keywords> <string>0x20000000000000</string> <string>0x10000000000000</string> </keywords>

Please log a support case on this

You could insert node ID I believe, let me shoot this over to one of the Dev guys to comment on to keep me honest

This is still an open item in our system. Unfortunantly I cannot give any time frame on resolution

Please open a support ticket so we can investigate, have you applied SP4 to all the servers? Odd that a reboot would cause them to change

We are evaluating removing our usage of MSFT SNMP trap receiver and bolting in another, however, this is not a trivial task. How do you poll MSFT servers if it doesn't support SNMPv3?