Overview

This chapter explains how the NX-OS modular package management allows for the selective addition, removal, and upgrade of specific features without altering the base software. It also details the differences between Base and Full boot modes and the use of RPM and DNF tools to manage these optional packages for a leaner system footprint.

Optionality in NX-OS software

This section explains NX-OS software optionality, highlighting modular package management and how this capabily delivers flexibility, a leaner footprint, and asynchronous feature delivery.

Modular packages

This section explains the architecture and management of modular packages in NX-OS, which are independent software components (RPMs) that allow for feature-specific upgrades and runtime removal.

NX-OS image boot modes

This section defines the base and full boot modes for NX-OS and provides the commands to switch between them. It explains how to reset the switch to install either a minimal set of core features or the complete software image.

Red Hat Package Managers

Learn about Red Hat Package Managers (RPMs) and how NX-OS that is built on a Linux kernel leverages the RPM framework to provide Optionality—the ability to customize the switch's software footprint by adding or removing components without needing to replace the entire system image.

Dandified YUM commands

This section explains the Dandified YUM (DNF)commands that replaced the YUM commands beginning with NX-OS Release 10.1(x).

Configure an FTP server and set up a local FTP YUM repository

This section outlines the steps to create an FTP server and configure a local FTP YUM repository for managing NX-OS software packages.

Create user roles for install operation

This section specifies that access to the install command is restricted to the admin role unless granted to other users through Role-Based Access Control (RBAC).