Cisco Spaces Connector 3.X ESX OVA templates

[blakemweston]

Hi,

I have been reading though the various documentation for Spaces Connector and there doesnt appear to be any information with regards to the sizing / usage of the three OVA options (Standard, Advanced1, Advanced2). Can anyone provide the justification for when the different profiles should be used? I am sizing up a solution and need to determine how much VM resources will be needed for the Connector

I have also noticed the Compatibility Matrix for Connector 3 does not appear to have been updated, for example it does not list 17.6.4 or 17.9.X

[ammahend]

couldn't find exact info, but I will just deploy Advanced 2,  its hardly a desktop form factor compute resources anyways.

https://www.cisco.com/c/en/us/td/docs/wireless/spaces/connector/config/b_connector_30/m_prerequisites30.html

documentations are not always updated however considering 3.0 is latest connector is should be compatible with 17.9.X, I asked this question in Partner VT Webex room if someone replies I will update you, but you are right its not documented anywhere officially.

In my deployment I did standard for 3000 APs and it works with no issues.

[blakemweston]

Since I am developing a design to justify the deployment I cannot just select the larger option without backing requirements, hence why I am asking. Looks like I'll have to bring this up with our Cisco AM or SE, which also brings up another thought whether this is capable of supporting hyperthreading....

[Rich R]

Best to ask them about the hyperthreading too.

Some Cisco products recommend it but for 9800-CL hyperthreading is explicitly "not supported" and although it may actually work it's one of those things where if it goes wrong TAC will just say "that's not supported".

[blakemweston · Accepted solution]

Just a follow up on this topic. Cisco don't really have a defined sizing of Connector 3 which is a bit worrying. Recommendation from a Spaces specialist was to deploy a standard size Connector for Location Services alone, and then a separate Connector for IoT. I didnt get a response when I stated this doesnt follow the documentation as the new Connector is meant to be built for multiservice and this just adds things to be monitored / maintained (flashbacks to Prime....)

I did get it confirmed that Connector 3 is supported with hyperthreading enabled on the ESX host.