What's New in Release 2.3.2
This release allows you to perform the following:
-
Deploy the connector as a Amazon Web Services (AWS) instance. You can download an Amazon Machine Images (AMI) image from Amazon Web Services. The connector AMI has the following limitations:
-
Dual-interface mode is not supported.
-
Proxy configuration is not supported.
-
Enabling or disabling the AAA with IPSec feature is not supported.
-
Upgrading the connector from theGUI is not supported.
For more information, see Downloading and Deploying the Cisco Spaces: Connector AMI.
-
-
Install a connector in a dual-interface mode, where the connector has access to two different networks.
-
Configure the connector to access an external network that can reach the cloud-hosted Cisco Spaces, and an internal network that connects to all your devices (dual-interface mode). For more information, see Downloading and Deploying the Cisco Spaces: Connector OVA (Dual Interface) .
-
Deploy the connector as a Hyper-V instance. You can download a Virtual Hard Disk (VHDX) image from cisco.com . However, you cannot configure the Hyper-V connector in the dual-interface mode. For more information, see Downloading and Deploying Hyper-V.
-
Configure a syslog server on the connector. For more information, see Syslog Commands in Connector Command Reference Guide.
-
Mask a user's IP address on Cisco Spaces (along with username and MAC address). For more information, seeConfiguring Privacy Settings in the Connector Configuration Guide.
-
Configure the HTTP proxy with basic authentication. See Configuring a Proxy in the Connector Configuration Guide.
-
Test connectivity from connector to Cisco Spaces using the connectorctl testconnectivity command. For more information, see Cloud Connectivity Commands in the Connector Command Reference Guide.
-
Configure the Subject Alternative Names (SANs) field of a self-signed certificate or a Certification Authority (CA)-signed certificate with either the Fully Qualified Domain Name (FQDN) or the hostname of the connector. The connectorctl createcsr and the connectorctl generatecert commands are now modified with the capability to configure Subject Alternative Names (SANs). For more information, see Certificate Commands in the Connector Configuration Guide.