What's New in Cisco iNode Manager


Note


Explore the Content Hub, the all new portal that offers an enhanced product documentation experience.

  • Use faceted search to locate content that is most relevant to you.

  • Create customized PDFs for ready reference.

  • Benefit from context-based recommendations.

Get started with the Content Hub at content.cisco.com to craft a personalized documentation experience.

Do provide feedback about your experience with the Content Hub.


Cisco is continuously enhancing the product with every release and this section covers a brief description of key features and enhancements that were added. It also includes links to detailed documentation, where available.

New Software Features in Cisco iNode Manager 23.1

Feature

Description

Infrastructure Enhancements
Inode-service-manager pod auto restart

In iNode Manager 23.1, the validity of certificate is auto-renewed. In iNode Manager 22.4, user needs to manually restart the inode-service-manager pod to renew the certificate validity for another 11 months. In iNode Manager 23.1, the process of restarting the inode-service-manager pod is automatically done. Auto renewal period is 270 days.

Inode-service-manager log file will be added with a log entry “Restarting inode-service-manager POD to auto-renew the certificate” whenever auto-renewal happens.

Certificate Signing Requests You can initiate the TLS Certificate creation process from Operations Hub. Once a certificate request is completed, you can download it and get it signed by an appropriate signing authority. Once signed, you can upload the certificate and override the default self-signed Ingress Certificate.
LDAP Connectivity checks When adding an LDAP configuration, you can perform a connectivity check and verify end-to-end LDAP connectivity. You need valid user credentials along with LDAP configuration, to perform the connectivity check. If you trigger Validate LDAP Configuration and if there is LDAP connectivity failure, then an error message with the reason of failure is displayed
K8 Version K8 version is upgraded to 1.22.
Single NIC for NB and SB communication for AIOs By default, All-in-one clusters are deployed with two vNICs. One vNIC must be logically connected to a management network, while the other must be logically connected to the CIN. If you have a shared management and CIN network, you can optionally deploy an AIO cluster with a single vNIC.
Path Based URL Enhancements

Deployer VM supports path-based URL. iNode manager only needs two DNS entries as a prerequisite for installation.

- cluster.example.com (DNS entry for Cluster)

- deployer.example.com (DNS entry for Deployer)

vSphere Data Center Folder Path support Operations Hub’s Autodeployer supports the ability to deploy Ops Hub clusters into a defined vSphere datacenter folder path.

Feature

Description

Debuggability Enhancements
TAC Debug Package TAC Debug Packages are collections of logs and other operational data that can be easily shared with Cisco TAC Engineers. You can collect the information from Operations Hub GUI. The latest TAC Debug package is visible on top. You can delete or download the package on demand.

Feature

Description

iNode manager upgrade
iNode manager upgrade iNode manager 23.1 is upgrade ready. You can upgrade to Cisco iNode manager 23.1 from Cisco iNode manager 3.2.0 and Cisco iNode manager 22.4.