Download Cisco Intersight

Author: s | 2025-04-24

Cisco Intersight API Overview . This document provides an overview of the Cisco Intersight API. For general information on Intersight, visit Cisco Intersight - Cisco . API

CiscoDevNet/intersight-powershell: Cisco Intersight

Central. Once the Cisco DC is installed, it builds a bi-directional secure communication channel bridging Cisco Intersight with Nutanix Prism Central. Cisco Intersight uses Prism Central v4 Management APIs to display and monitor different Intersight services for Cisco HCI clusters running Nutanix software (as also described under Benefits). The development of a bi-directional interface between the Cisco Intersight management platform and Nutanix Prism Central enables both Cisco and Nutanix to develop observability and monitoring features independently in future. Supported hardware ● All Cisco HCI servers are officially supported ◦ HCI M6 and M7 rack servers ◦ HCI M7 X-series modular servers ● UMM (UCSM Managed Mode), ISM (Intersight Standalone Mode), and IMM (Intersight Managed Mode) clusters are supported Supported software ● Nutanix software ◦ Prism Central 2024.3 or later ◦ AOS 6.8 or later ◦ Lifecycle Manager (LCM) 3.1 or later (for device connector upgrades) ◦ Cisco Device Connector (DC) 4.3.0 or later ◦ Support for both- Nutanix Acropolis Hypervisor (AHV) and ESXi hypervisor ● Cisco software ◦ Support for Cisco Intersight SaaS ◦ Support for Cisco Intersight Connected Virtual Appliance (CVA) and Private Virtual Appliance (PVA) (1.1.2-0 or later) Cisco Intersight and Nutanix Prism Central Day 1 integration scale limits ● Phase 1 support (initial release) – support each Prism Central with 25 registered clusters and 5000 alarms Learn more For information on Cisco Compute Hyperconverged Infrastructure with Nutanix, visit cisco.com/go/computehyperconverged. For information on Cisco Intersight, visit

Cisco Intersight - Cisco Intersight and Nutanix Prism Central (PC

Cisco Intersight Cisco Intersight is a Software-as-a-Service (SaaS) infrastructure management platform that is augmented by other intelligent systems. It provides global management of the Cisco Unified Computing System (Cisco UCS) and Cisco HyperFlex hyperconverged infrastructure, Cisco APIC, and other platforms including Nexus Dashboard. Data center apps, such as Cisco Nexus Dashboard Insights, connect to the Cisco Intersight portal through a Device Connector that is embedded in the management controller of each system, in this case your Nexus Dashboard platform. Device Connector provides a secure way for the connected devices to send information and receive control instructions from the Cisco Intersight portal, using a secure internet connection. When an Intersight-enabled device or application starts, the Device Connector starts at boot by default and attempts to connect to the cloud service. If the Auto Update option is enabled, the Device Connector is automatically updated to the latest version through a refresh by the Intersight service when you connect to Cisco Intersight. For more information on the Auto Update option, see Configuring Device Connector Settings. For additional information on Cisco Intersight, see Note If you upgraded from Application Services Engine and your Intersight device connector is claimed with a proxy configured, you will need to re-configure the proxy in the Cluster Configuration screen. For more information, see Cluster Configuration. Configuring Device Connector Settings Devices are connected to the Cisco Intersight portal through a Device Connector, which provides a secure way for the connected devices to send information and receive control instructions from the Cisco Intersight portal. All device connectors must properly resolve svc.intersight.com and allow outbound initiated HTTPS connections on port 443. If a proxy is required for an HTTPS connection, you must configure the proxy settings in your Nexus Dashboard. This section describes how to configure the basic Device Connector settings. Navigate to your Nexus Dashboard’s Admin Console. From the main navigation menu, select Infrastructure > Intersight. In the top right of the main pane, click Settings. Click the General tab to configure basic options. Use the Device Connector knob to enable or disable the Device Connector. This enables you to claim

Intersight At-a-Glance - Cisco

SaaS platform and your on-prem deployed UCS Director software, to deliver on-going new capabilities and benefits.As we continue to enhance Cisco Intersight and UCS Director functionality, this hybrid SaaS model provides significant better together benefits for our customers. The “symbiotic” relationship between Cisco Intersight and UCS Director 6.7 today delivers following benefits:Automated UCS Director patch/upgrade image delivery that allows customers to control their upgrades within operational processes and maintenance schedulesEnhanced Customer eXperience (CX) where in Intersight SaaS enables Cisco TAC to streamline diagnostics log collection and expedited issue resolution for customer on premise installed UCS Director softwareCisco expects to deliver more “better together” benefits and functionality down the road, as we simplify data center automation and private cloud IaaS experience. This will enable a smooth journey for UCS Director customers, as they leverage Cisco Intersight SaaS for better together benefits. These benefits are delivered with the great attention to ensuring security that Cisco offers for all our SaaS platforms. This video provides more details.What’s New?Cisco continues to deliver on our strategy with the latest release of Cisco UCS Director, version 6.7. This release is another step in the private cloud IaaS evolution we described in this blog nine months ago. In this video we explain how to use Cisco Intersight SaaS platform to automate UCS Director update and patch image delivery.The latest UCS Director 6.7 release includes an optimized multi-node architecture large scale Data Center automation and Private Cloud IaaS, strengthens security hardening across entire software stack, data base and enables Self-signed Certificate use. There are further enhancements to orchestration and automation functionality to allow cloning tasks, configurable loop task parameters, and full read access to orchestration tasks for the end-user portal.UCS Director 6.7 also supports for the following:Automation Task Library for UCS firmware updatesCisco ACI 4.0, ACI Multi-Site Controller, Policy Based Routing (PBR) associated tasks/workflows, and moreRed Hat Enterprise KVM guest customizationVMware 6.7 vCenter certificationFor more information see the following:UCS Director data sheetUCS Director compatbility matrix Share: Authors. Cisco Intersight API Overview . This document provides an overview of the Cisco Intersight API. For general information on Intersight, visit Cisco Intersight - Cisco . API Cisco Intersight Video Playlist (YouTube channel Cisco Intersight, HyperFlex UCS) Cisco DevNet – Cisco Intersight; Cisco Intersight hands-on lab s (list below based on

Cisco Intersight Virtual Appliance and Intersight Assist

Cisco continues to invest and enhance our data center automation and private cloud infrastructure as a service (IaaS) platform, Cisco UCS Director. At the same time, we are leveraging the Cisco Intersight platform to deliver additional value and operational benefits when coupled with UCS Director.Guest Blogger: Sri Hary Vengadasubbu, Cisco Intersight Product ManagementExecuting on Our StrategyWe introduced Cisco Intersight software as a service (SaaS) systems management platform that unifies the Cisco UCS rack and blade servers and HyperFlex hyperconverged infrastructure for our customers. In a series of blogs, the product management team has explained our strategy for helping our customers transition from Cisco UCS Director to Cisco Intersight. Here’s the list of blogs from the series:UCS Director – A Strategic IaaS EvolutionUCS Director – Simplify Infrastructure Automation AnywhereCisco Intersight and UCS Director: Executing on Our StrategyInvestment ProtectionCisco is committed to delivering private cloud IaaS automation offered by UCS Director and in protecting our customers investments. A new Intersight Advantage edition to be announced shortly will include UCS Director, in addition to other capabilities, and it will extend customer’s investment protection as they transition to Cisco Intersight. Over time, the combination of UCS Director and Intersight will simplify day to day operations and extend private cloud IaaS services.Bringing SaaS Benefits to UCS Director: Hybrid SaaSOne of the advantages of the Cisco Intersight SaaS platform is that customers get the benefits of continuous integration and continuous delivery (CI/CD). This means they can realize the advantages of new, enhanced capabilities as they are made available every couple of weeks without creating additional work for operations teams. Customers using on-prem enterprise software like UCS Director traditionally go through a delayed patch and upgrade process. As a result, they do not realize the benefits of new capabilities for 3-6 months, or even longer, after a product release, due to delays in operational processes.Starting with latest Cisco UCS Director 6.7 release, customers can now get SaaS and CI/CD benefits by simply “claiming” their UCS Director on-prem installation from the Cisco Intersight SaaS platform. This claim process enables a secure hybrid SaaS setup by associating the Intersight

Cisco Intersight - Cisco Video Portal

The need for visibility and insights IT organizations must ensure they are delivering digital experiences that delight customers. Delivering outstanding digital experiences can boost customer satisfaction and enhance brand reputation, potentially leading to increased sales and revenue. Operational costs can decrease due to fewer support requests, and the insights gained can drive strategic business decisions. However, complex IT operations and lack of visibility can: ● Obscure the ability to swiftly identify and resolve system issues, leading to prolonged downtimes and poor user experiences ● Result in inconsistent system performance, reduce resource optimization, and hinder informed decision-making ● Lead to security vulnerabilities going unnoticed, risking data breaches and loss of customer trust Simplified operations with enhanced monitoring is essential to optimize performance and proactively manage your technology landscape from a centralized vantage point. Cisco Intersight and Nutanix Prism Central (PC) integration Cisco® and Nutanix have collaborated to introduce foundational integration capabilities between Cisco Intersight® and Nutanix Prism, delivering greater visibility and insight into the Cisco Compute Hyperconverged with Nutanix solution. This integration will deliver a more unified experience to customers implementing the solution and provide increased visibility and control across distributed hyperconverged clusters. Benefits ● Simplify operations: Single dashboard on Cisco Intersight for monitoring Cisco Hyperconverged Infrastructure (HCI) running Nutanix software from multiple Nutanix Prism Centrals (PCs) ● Enhance visibility: Bi-directional interface enables the ability to see Cisco HCI Nutanix cluster and node detail view; storage utilization; cluster-level alarm aggregation and alarm acknowledgement, and Nutanix license entitlement, compliance, and violations. ● Ease of use and flexibility: A single view to manage Cisco Intersight licenses and Nutanix licenses; automatic upgrade of Cisco Device Connector (DC) via Intersight; and support for Cisco Intersight SaaS, Cisco Intersight Connected Virtual Appliance (CVA), and Private Virtual Appliance (PVA) ● Efficient troubleshooting: Future cross-launch capabilities will facilitate quicker debugging and issue resolution across both platforms. What it does Nutanix Prism Central (PC) can be a managed target connected to the Intersight portal through a Cisco Device Connector. The Cisco Device Connector (DC) application (Opt-in) must be downloaded from the Prism Central Marketplace and installed in Nutanix Prism

Cisco Intersight - A Deeper Dive - Cisco

Default value is 8080. Note If Proxy is enabled with the smart license configuration on Cisco Nexus switches, the NXDC inherits this configuration and attempts to connect with Cisco Intersight Cloud. Step 3 (Optional) intersight use-vrf Example: switch(config)# intersight use-vrf blue (Optional) Modifies the VRF of NXDC, if connectivity is through the specified VRF. Note By default Intersight is started in management VRF/namespace. Step 4 (Optional) intersight trustpoint [host-name] Example: switch(config)# intersight trustpoint test test (Optional) Configures certificates for Intersight connection. trustpoint-label: Crypto ca truspoint label. For more information refer to Cisco Nexus 9000 Series NX-OS Security Configuration Guide. Step 5 (Optional) intersight source-interface Example: switch(config)# intersight source-interface mgmt 0 (Optional) Configures the source interface for communication. Step 6 (Optional) no feature intersight Example: switch(config)# no feature intersight (Optional) Disables the Intersight process and removes all NXDC configuration and logs store. Verifying NXDC configuration and status To verify the NXDC configuration, use the following Bash commands: To display the NXDC configuration and status information, enter one of the following commands: Command Purpose show system device-connector claim-info Displays the device Serial Number, Token and Intersight claim state. Note Token will be displayed when connectivity to Intersight is established and the device is not claimed. In the scenario that a device is claimed, a Token will not be displayed and the message section will display "Cannot fetch claim code for already claimed device". Duration for valid token is reported in seconds. show system device-connector log [dc|dcgrpc|cnmi|nae|sim|compliance] Displays device connector log messages. The following example shows sample output for the show system device-connector claim-info command before device is claimed:Switch# show system device-connector claim-infoSerialNumber: FDO23021ZUJSecurityToken: 9FFD4FA94DCDDuration: 599Message:Claim state: Not Claimed The following example shows sample output for the show system device-connector claim-info command after device is claimed:Switch# show system device-connector claim-infoSerialNumber: ABCD12345E6SecurityToken:Duration: 0Message: Cannot fetch claim code for already claimed deviceClaim state: ClaimedClaim time: 2024-02-18T12:00:01.77ZClaimed by: [email protected]: dc- customerSite name:Site ID: Claiming Nexus Switches in Intersight To get started with using the features and functionality, you must claim the switch in an Intersight User Interface (UI). To claim the switch in Intersight UI, use the following procedure: Claim Nexus switches using Intersight UI. To claim the connected devices in Intersight, follow the process as described in Target Claim. Claim multiple Nexus switches with Ansible playbook. To claim multiple Nexus switches in an automated manner using Ansible, check the details in the Ansible playbook.

Cisco Intersight Virtual Appliance and Intersight Assist Getting

Nexus Switch Intersight Device Connector This chapter contains the following sections: Nexus Switch Intersight Device Connector Overview Devices are connected to the Cisco Intersight portal through a Nexus Switch Intersight Device Connector (NXDC) that is embedded in the Cisco NX-OS image of each system. Beginning with Cisco NX-OS Release 10.2(3)F, the Device Connector on NX-OS feature is supported which provides a secure way for the connected devices to send information and receive control instructions from the Cisco Intersight portal, using a secure Internet connection. The NXDC is enabled by default on all Cisco Nexus series switches and it starts at boot by default, and attempts to connect to the cloud service. Once a secure connection has been established and the device connector is registered with the Intersight service, the device connector collects detailed inventory, health status and sends the adoption telemetry data to the Intersight database. Inventory is refreshed once in a day. The NXDC supports the AutoUpdate feature where it gets automatically updated to the latest version through a refresh by the Intersight service when you connect to Intersight. The NXDC also supports the Connected TAC feature to collect tech-support data from devices that are claimed. The NXDC feature integration was done to resolve the standalone Nexus switches with the following capabilities: It provides fast and quick solution to gather basic data from standalone Nexus switches. It stores and manages private data securely in the cloud. It is flexible for future capabilities and enables the ability to upgrade NXDC. Guidelines and Limitations NXDC has the following guidelines and limitations: You must configure DNS. You must ensure svc.intersight.com gets resolved and allow outbound initiated HTTPS connections on port 443. If a proxy is required for an HTTPS connection to svc.intersight.com, the proxy can be configured in the NXDC user interface. For proxy configuration, see Configuring NXDC. Configuring Nexus Switch to Intersight By default the Nexus switch attempts to connect to Cisco's Intersight. If your Nexus device does not have the ability to reach Intersight, a specific proxy for Intersight must be configured. Note By default the Intersight feature (also known as Nexus Device Connector) is enabled. To configure the optional parameters for the Intersight feature, follow the below steps: SUMMARY STEPS configure terminal (Optional) intersight proxy port (Optional) intersight use-vrf (Optional) intersight trustpoint [host-name] (Optional) intersight source-interface (Optional) no feature intersight DETAILED STEPS Command or Action Purpose Step 1 configure terminal Example: switch# configure terminalswitch(config)# Enters global configuration mode. Step 2 (Optional) intersight proxy port Example: switch(config)# intersight proxy proxy.esl.cisco.com port 8080 (Optional) Configures the proxy server for Intersight connection. proxy-name: IPv4 or IPv6 address or DNS name of proxy server. proxy-port: Proxy port number. The range is 1-65535. The. Cisco Intersight API Overview . This document provides an overview of the Cisco Intersight API. For general information on Intersight, visit Cisco Intersight - Cisco . API

Cisco Intersight IT operations platform

The device and leverage the capabilities of Intersight. If it is disabled, no communication is allowed to Cisco Intersight. In the Access Mode area, choose whether to allow Intersight the capability to make changes to this device. Allow Control (default) — enables you to perform full read or write operations from the cloud based on the features available in Cisco Intersight. Read-only — ensures that no changes are made to this device from Cisco Intersight. For example, actions such as upgrading firmware or a profile deployment will not be allowed in read-only mode. However, the actions depend on the features available for a particular system. Use the Auto Update knob to enable automatic Device Connector updates. We recommend that you enable automatic updates so that the system automatically updates the Device Connector software. When enabled, the Device Connector will automatically upgrade its image whenever there is any upgrade push from Intersight. If you disable the automatic updates, you will be asked to manually update the software when new releases become available. Note that if the Device Connector is out-of-date, it may be unable to connect to Cisco Intersight. Click Save to save the changes. Click the Certificate Manager tab if you want to import additional certificates. By default, the device connector trusts only the built-in certificate. If the device connector establishes a TLS connection and a server sends a certificate that does not match the built-in certificate, the device connector terminates TLS connections because it cannot determine if the server is a trusted device. You can choose to upload additional certificates by clicking the Import button in this screen. The imported certificates must be in the .pem (base64 encoded) format. After a certificate is successfully imported, it is listed in the list of Trusted Certificates and if the certificate is correct, it is shown in the In-Use column. You can click the View icon at the end of the certificate’s row to view its details such as name, issue and expiration dates. Target Claim This section describes how to claim the Nexus Dashboard platform as a device for Cisco Intersight.

Cisco Intersight – A Transformative Evolution

Requirements. Attention Ensure that the following requirements for using DHCP are met: If you use DHCP, ensure that the IP address returned to the appliance VM resolves to the same FQDN you use to set up the appliance. Cisco recommends that you configure your DHCP to return the same IP address for the appliance VM, and not change your IP address frequently. The appliance only reads the IP address, netmask, gateway, and DNS-Servers from the DHCP lease information. NTP information for the Hyper-V Server must be input into the Virtual Machine Connection console when configuring static IP. All IP addresses used in the appliance VM must be in the same subnet as that of the initial IP addresses assigned. For example, the VM cannot be assigned an IP from a different subnet, by connecting to a vSwitch which has a different DHCP server. Limitations A forced lease renewal could impact the VM configuration settings and could render the appliance unusable. Step 7 Proceed to to complete the post-install set-up of your appliance. For information on how to complete the set-up of your appliance, see Setting Up Intersight Virtual Appliance. After providing the password and IP property parameters, if you notice that your VM does not respond when you visit after about 15 minutes, you can use the Intersight Appliance Maintenance Shell to troubleshoot networking or misconfiguration issues. The diagnostic tool aims to: Detect and display issues with the installation prerequisites. Enable editing the inputs that are provided during the OVA deployment. Assist with continuing the installation after you fix the settings, or set network interface properties such as IP addresses, subnet mask, and default gateway during the OVA deployment. For more information, see Intersight Appliance Maintenance Shell. For a demonstration of the Intersight Virtual Appliance Installation and troubleshooting, watch Cisco Intersight Appliance Installation and Debug. Installing Cisco Intersight Virtual Appliance on KVM Hypervisor Cisco Intersight Virtual Appliance is distributed as a deployable virtual machine contained in an Open Virtual Appliance (OVA) file format, ZIP file format, or a TAR file format. Install the appliance on KVM hypervisor using the TAR file format. The following procedure shows how to install and deploy the appliance on KVM hypervisor using Virtual Machine Manager (VMM). Note Software Requirements: Linux operating system with support for KVM hypervisor or Linux operating system pre-configured with KVM hypervisor. On CentOS 7.9, the minimum supported KVM hypervisor version is 1.5.3. A virtual network bridge to provide network connectivity to VMs. Before you begin Ensure that you have downloaded the Cisco Intersight Virtual Appliance package from the URL provided by your Cisco representative or a location accessible from your setup, such as a local hard drive, a network share, or a CD/DVD drive. Attention Setting up Cisco Intersight Virtual Appliance requires an IP address and 2 hostnames for that IP address. The hostnames must be in the following formats: myhost.mydomain.com—A hostname in this format is used to access the GUI. This must be defined as an A record and PTR. Cisco Intersight API Overview . This document provides an overview of the Cisco Intersight API. For general information on Intersight, visit Cisco Intersight - Cisco . API

Introduction to Cisco Intersight - YouTube

Change your IP address frequently. The appliance only reads the IP address, netmask, gateway, and DNS-Servers from the DHCP lease information. NTP information, if any, must be input into the OVF parameters at the time of the deployment. All IP addresses used in the appliance VM must be in the same subnet as that of the initial IP addresses assigned. For example, the VM cannot be assigned an IP from a different subnet, by connecting to a vSwitch which has a different DHCP server. Limitations A forced lease renewal could impact the VM configuration settings and could render the appliance unusable. Step 12 On the Ready to Complete page, select Power On After Deployment and click Finish. For information on how to complete the set-up of your appliance, see Setting Up Intersight Virtual Appliance. After providing the OVF parameters, if you notice that your VM does not respond when you visit after about 15 minutes since power-on, you may use the Intersight Appliance Maintenance Shell to troubleshoot networking or misconfiguration issues. The diagnostic tool aims to: Detect and display issues with the installation prerequisites. Enable editing the inputs that are provided during the OVA deployment. Assist with continuing the installation after you fix the settings, or set network interface properties such as IP addresses, subnet mask, and default gateway during the OVA deployment. For more information, see Intersight Appliance Maintenance Shell. For a demonstration of the Intersight Virtual Appliance Installation and troubleshooting, watch Cisco Intersight Appliance Installation and Debug. Installing Cisco Intersight Virtual Appliance on Microsoft Hyper-V Server Cisco Intersight Virtual Appliance is distributed as a deployable virtual machine contained in an Open Virtual Appliance (OVA) file format, ZIP file format, or a TAR file format. Install the appliance on Microsoft Hyper-V Server using the ZIP file format. For more information about Microsoft Hyper-V Server, refer to the Microsoft documentation. Use the following procedure to install and deploy the appliance on Hyper-V Server Manager. Before you begin Ensure that you have downloaded the Cisco Intersight Virtual Appliance package from the URL provided by your Cisco representative or a location accessible from your setup, such as a local hard drive, a network share, or a CD/DVD drive. Attention Setting up Cisco Intersight Virtual Appliance requires an IP address and 2 hostnames for that IP address. The hostnames must be in the following formats: myhost.mydomain.com—A hostname in this format is used to access the GUI. This must be defined as an A record and PTR record in DNS. The PTR record is required for reverse lookup of the IP address. If an IP address resolves to multiple hostnames, the first one in the list is used. Note For Intersight Virtual Appliance versions up to 1.0.9-148 only—See RFC 1123 for details about Regular Expression for a valid hostname. dc-myhost.mydomain.com—The dc- must be prepended to your hostname. This hostname must be defined as the CNAME of myhost.mydomain.com. Hostnames in this format are used internally by the appliance to manage device connections. Ensure that the