Device Connector

Device Connector

Device connector connects Cisco UCS Manager to Cisco Intersight, the cloud-hosted server management system. It enables Cisco UCS Manager to be managed and monitored through Cisco Intersight.

To register a device with Cisco Intersight in the cloud, you must do the following:

  1. Connect Cisco UCS Manager with Cisco Intersight by configuring the device connector proxy settings, if they are required.

  2. Use the device serial number and security code to validate your access to the device from Cisco Intersight and claim the device.

Updating Device Connector

When you upgrade Cisco UCS Manager, the device connector is automatically updated to the image integrated with the Cisco UCS Manager version. The device connector does not get downgraded when you downgrade the Cisco UCS Manager version.

You can update the device connector through the Cisco Intersight GUI. You can also update the device connector through the local management shell in Cisco UCS Manager CLI.

Procedure

  Command or Action Purpose
Step 1

UCS-A# connect local-mgmt

Enters local management mode.

Step 2

UCS-A(local-mgmt)# copy [from-filesystem:] [from-path] filename to-path [dest-filename]

Copies the device connector image file from a remote server to a local destination by using the specified file transfer protocol. You need to copy the file to one fabric interconnect only.

  • from-filesystem—The remote file system containing the file to be copied.

    This file system can be specified by using one of the following options:

    • ftp: [ // [ username@ ] server ]

    • scp: [ // [ username@ ] server ]

    • sftp: [ // [ username@ ] server ]

    • tftp: [ //server [ :port ] ]

    If the file system is not specified, the current working file system is assumed.

    If a remote protocol is specified with no server name, you are prompted to enter the server name.

  • from-path—Absolute or relative path to the file to be copied. If no path is specified, the current working directory is assumed.

  • filename—The name of the source file to be copied.

  • to-path—Absolute or relative path to the copied file. If no path is specified, the current working directory is assumed. The path includes the local file system to contain the copied file.

    This file system can be specified from one of the following options:

    • volatile:

    • workspace:

  • dest-filename—The new name for the copied file. If a dest-filename is specified, the copied file is renamed at the destination location.

Note 

You cannot download the device connector image file through Cisco UCS Manager GUI.

Step 3

UCS-A(local-mgmt)# update-device-connector workspace: | volatile: /filename [skip-upgrade-on-peer ]

Updates the device connector image on the peer fabric interconnect and then the local fabric interconnect.

Using the skip-upgrade-on-peer option skips update on the peer fabric interconnect.

Example

The following example updates the device connector on both fabric interconnects: 

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 peer Fabric interconnect
Successfully updated device connector on peer Fabric interconnect
Updating Device Connector on local Fabric interconnect
Successfully updated device connector on local Fabric interconnect
UCS-A(local-mgmt)#

The following example updates the device connector on the local fabric interconnect only: 

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 skip-upgrade-on-peer
Update Started
Updating Device Connector on local Fabric interconnect
Successfully updated device connector on local Fabric interconnect
UCS-A(local-mgmt)#