Device Connector Requirements
You can claim a target in Cisco Intersight Virtual Appliance through the embedded device connector. Before you claim a target, ensure that the device connector requirements are met. The following table lists the software compatibility and the supported device connector versions for Intersight Virtual Appliance:
Component |
Minimum software version for Connected Virtual Appliance |
Minimum software version for Private Virtual Appliance |
Supported Device Connector version |
Minimum supported versions that include supported Device Connectors |
---|---|---|---|---|
Cisco UCS Manager |
3.2(1) |
4.0(2a) |
1.0.9-2290 |
4.0(2a) |
Cisco IMC Software |
For M5 Servers: 3.1(3a) For M4 Servers: 3.0(4) |
4.0(2d) |
1.0.9-335 |
4.0(2d) |
HyperFlex Connect and Data Platform |
2.6 |
3.5(2a) |
1.0.9-1335 |
3.5(2a) |
CIsco UCS Director |
6.7.2.0 |
6.7.2.0 |
1.0.9-911 |
6.7.2.0 |
Device Connector Upgrade
When the Device Connector on an endpoint is not at the compatible version, you can upgrade it in the following ways:
-
Perform a complete firmware upgrade to the version that has the supported Device Connector. This process could involve updating your configuration settings.
-
Manually upgrade the Device Connector. This option is supported only on Cisco UCS Manager. For more information, See Manual Upgrade.
-
Cisco Intersight Virtual Appliance supports upgrading the device connector from the cloud. When the target claim process detects that the device connector at the endpoint is not at the compatible version, it triggers an upgrade of the device connector from Intersight cloud. To facilitate this upgrade, port 80 must be open between the appliance and the endpoint target. The HTTPS proxy running on port 80 requires that your firewall settings allow communication through port 80.
Device Connector upgrade from Intersight cloud is optional. During the upgrade from the cloud, some target data (server inventory) from the appliance leaves your premise. When you choose this option the following data leaves your premises:
-
The endpoint target type - Cisco UCS Fabric Interconnect, Integrated Management Controller, Cisco HyperFlex System, Cisco UCS Director
-
The firmware version(s) of the endpoint
-
The serial number(s) of the endpoint target
-
The IP address of the endpoint target
-
The hostname of the endpoint target
-
The endpoint device connector version and the public key
Attention
Target claim could fail if the device connector is at an older version that does not support the appliance, and you have disabled the data collection option during the initial setup. This failure is caused due to details about the endpoint being required to leave the premises for the one time upgrade to work. To avoid a target claim failure, select the Enable Data Collection option temporarily or upgrade the device connector in the other methods mentioned above.
-
Manual Upgrade of Device Connector (applicable only to Cisco UCS Fabric Interconnect)
Log in to your UCS Fabric Interconnect as an admin user and run the following command:
UCS-A# connect local-mgmt
UCS-A(local-mgmt)# copy scp://username@10.100.100.100/filepath/filename.bin workspace:/
UCS-A(local-mgmt)# update-device-connector workspace:/filename.bin
Update Started
Updating Device Connector on local Fabric interconnect
Successfully updated device connector on local Fabric interconnect
UCS-A(local-mgmt)#