Cisco Intersight Management

Intersight Management Mode

Cisco Intersight™ is a management platform delivered as a service with embedded analytics for your Cisco and 3rd party IT infrastructure. Intersight Managed Mode (IMM) is a new architecture that manages the UCS Fabric Interconnected systems through a Redfish-based standard model. Intersight Managed Mode unifies the capabilities of the UCS Systems and the cloud-based flexibility of Intersight, thus unifying the management experience for the standalone and Fabric Interconnect attached systems. Intersight Management Model standardizes policy and operation management for Cisco UCS 6600 Series Fabric Interconnect, UCSX-S9108-100G, UCS-FI-6454, UCS-FI-64108, UCS-FI-6536 and Cisco UCS B-Series (M5, M6), Cisco UCS C-Series (M5, M6, M7,M8), and Cisco UCS X-Series (M6 ,M7 ,M8) servers.

You can choose between the native UCSM Managed Mode (UMM) or Intersight Managed Mode (IMM) for the Fabric attached UCS Systems during initial setup of the Fabric Interconnects. If you choose to switch back between UMM and IMM, you must erase the present configuration and start from initial setup. Before erasing the configuration, you must ensure to unclaim the device from Intersight and decommission all rack servers.


Note

For more information, see https://intersight.com/help/resources#intersight_managed_mode.

Cisco Intersight Managed Mode (IMM) transition tool helps bootstrap new IMM deployments by replicating the configuration attributes of the existing Cisco UCS Manager (UCSM) infrastructure and by converting the existing Service Profile Templates to IMM Server Profile Templates to accelerate deployment of new servers in IMM.


Note

For more information, see the latest Cisco Intersight Managed Mode Transition Tool User Guide: https://www.cisco.com/c/en/us/td/docs/unified_computing/Intersight/b_cisco_intersight_managed_mode_transition_tool_user_guide.pdf

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.


    Note

    For Cisco UCS X-Series M7/M8 and/or Cisco UCS C-Series M7/M8 servers, Cisco UCS Manager requires Cisco Intersight connection and Intersight Infrastructure Service Licenses. When you Unclaim or Disable the device connector, ignoring the warning, a major fault is triggered.

  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)#

Local Management

traceroute

To view the route to a network host, use the traceroute command in local management command mode.

traceroute host-name [ source source ]

Syntax Description

host-name

The host name or IP address of the destination network host.

source source

(Optional) Specifies the IP address to be used as the source address in outgoing probe packets.

Command Default

None

Command Modes

Local management (local-mgmt)

Command History

Release Modification
1.0(1)

This command was introduced.

Usage Guidelines

Use this command to trace the route of IP packets to a network host.

You can use the optional source keyword to force the source address of the probe packets to be another IP address of the sending host.

Examples

This example shows how to trace the route to a network host:

switch-A(local-mgmt)# traceroute 10.64.58.50
traceroute to 10.64.58.50, 30 hops max, 60 byte packets
 1  10.197.123.1   (10.197.123.1)   0.284 ms 0.317 ms  0.351 ms
 2  10.127.103.165 (10.127.103.165) 0.277 ms 0.292 ms  0.388 ms
 3  10.127.42.101  (10.127.42.101)  0.721 ms 0.731 ms  0.761 ms
 4  10.127.42.101  (10.127.42.101)  0.803 ms 0.810 ms  0.813 ms
 5  10.127.188.30  (10.127.188.30)  0.813 ms 0.816 ms  0.829 ms
 6  * * *
 7  10.225.71.226 (10.225.71.226)   0.883 ms  0.979 ms  0.566 ms
 8  10.127.43.165 (10.127.43.165)   0.774 ms  0.750 ms  1.964 ms
 9  10.127.42.30  (10.127.42.30)    0.770 ms  0.732 ms  0.984 ms
10  72.163.187.110 (72.163.187.110) 1.005 ms  0.962 ms  0.972 ms
11  72.163.171.142 (72.163.171.142) 1.836 ms  1.827 ms  1.902 ms
12  10.64.58.50 (10.64.58.50)       1.620 ms  1.688 ms  1.727 ms

switch-A(local-mgmt)#